| 2.1 |
Approval of the agenda |
|
| R2-2402101 |
Agenda for RAN2#125bis |
Chairman |
| 2.2 |
Approval of the report of the previous meeting |
|
| R2-2402102 |
RAN2#125 Meeting Report |
MCC |
| R2-2403994 |
RAN2#125 Meeting Report |
MCC |
| 2.5 |
Others |
|
| R2-2403913 |
[Reserved] |
MCC |
| R2-2403916 |
[Reserved] |
MCC |
| R2-2403917 |
[Reserved] |
MCC |
| R2-2404005 |
[Reserved] |
MCC |
| R2-2404012 |
[Reserved] |
MCC |
| R2-2404013 |
[Reserved] |
MCC |
| R2-2404015 |
[Reserved] |
MCC |
| R2-2404016 |
[Reserved] |
MCC |
| R2-2404020 |
[Reserved] |
MCC |
| R2-2404021 |
[Reserved] |
MCC |
| R2-2404024 |
[Reserved] |
MCC |
| R2-2404025 |
[Reserved] |
MCC |
| R2-2404028 |
[Reserved] |
MCC |
| R2-2404029 |
[Reserved] |
MCC |
| R2-2404031 |
[Reserved] |
MCC |
| 3 |
Incoming liaisons |
|
| R2-2402124 |
Reply LS on the progress update of AI/ML Management specifications in SA5 (R3-241183; contact: ZTE) |
RAN3 |
| 4.1 |
EUTRA corrections Rel-17 and earlier |
|
| R2-2402815 |
Clarification of CQI report enabling in RRCEarlyDataRequest-NB message |
Qualcomm Incorporated |
| R2-2403488 |
Addition of polarization parameters |
Huawei, HiSilicon |
| R2-2403489 |
Addition of polarization parameters |
Huawei, HiSilicon |
| 4.1.1 |
Other |
|
| R2-2402987 |
Miscellaneous Corrections for TS 36.331 |
Samsung |
| R2-2402988 |
Miscellaneous Corrections for TS 36.331 |
Samsung |
| R2-2402989 |
Miscellaneous Corrections for TS 36.331 |
Samsung |
| R2-2402990 |
Miscellaneous Corrections for TS 36.331 |
Samsung |
| R2-2402991 |
Miscellaneous Corrections for TS 36.331 |
Samsung |
| R2-2403154 |
Discussion on LTE QoE configuration handling during inter-RAT mobility |
Huawei, HiSilicon |
| R2-2403484 |
Correction on LTE QoE configurations release in mobility from E-UTRA procedure |
Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2403485 |
Correction on LTE QoE configurations release in mobility from E-UTRA procedure |
Nokia, Nokia Shanghai Bell,Ericsson |
| R2-2403692 |
Correction on LTE QoE configurations release in mobility from E-UTRA procedure |
Nokia, Nokia Shanghai Bell, Ericsson |
| 5.1.1 |
Stage 2 and Organisational |
|
| R2-2402130 |
Reply LS on combination of HST and RRM relaxation (R4-2403532; contact: Apple) |
RAN4 |
| R2-2402524 |
Clarification on combination of HST and RRM relaxation |
CATT |
| R2-2402525 |
Clarification on combination of HST and RRM relaxation |
CATT |
| R2-2402526 |
Clarification on combination of HST and RRM relaxation |
CATT |
| R2-2402527 |
Clarification on combination of HST and RRM relaxation |
CATT |
| R2-2402528 |
Clarification on combination of HST and RRM relaxation |
CATT |
| R2-2402529 |
Clarification on combination of HST and RRM relaxation |
CATT |
| R2-2402869 |
Clarification on the combination of HST and RRM measurement relaxation |
Apple, Ericsson, Nokia (Rapporteur) |
| R2-2402870 |
Clarification on the combination of HST and RRM measurement relaxation |
Apple, Ericsson, Nokia (Rapporteur) |
| R2-2402871 |
Clarification on the combination of HST and RRM measurement relaxation |
Apple, Ericsson, Nokia (Rapporteur) |
| R2-2403362 |
Reference for User Service Description |
Nokia (Rapporteur) |
| R2-2403363 |
Reference for User Service Description |
Nokia (Rapporteur) |
| 5.1.1.1 |
Other |
|
| R2-2403004 |
Correction to UE capability description for fallback BC behavior |
Ericsson, Nokia (Rapporteur) |
| R2-2403005 |
Correction to UE capability description for fallback BC behavior |
Ericsson, Nokia (Rapporteur) |
| R2-2403006 |
Correction to UE capability description for fallback BC behavior |
Ericsson, Nokia (Rapporteur) |
| R2-2403007 |
Correction to UE capability description for fallback BC behavior |
Ericsson, Nokia (Rapporteur) |
| 5.1.2.1 |
MAC |
|
| R2-2403384 |
Clarification of Start Time of HARQ RTT Timer |
Samsung |
| 5.1.2.2 |
RLC PDCP SDAP BAP |
|
| R2-2403048 |
Corrections to data-volume calculation |
Nokia, Nokia Shanghai Bell |
| R2-2403049 |
Corrections to data-volume calculation |
Nokia, Nokia Shanghai Bell |
| R2-2403050 |
Corrections to data-volume calculation |
Nokia, Nokia Shanghai Bell |
| 5.1.3.1 |
NR RRC |
|
| R2-2402828 |
Clarification on plmn-IdentityIndex-r16 in SIB3 and SIB4 |
Huawei, HiSilicon |
| R2-2402829 |
Clarification on plmn-IdentityIndex-r16 in SIB3 and SIB4 |
Huawei, HiSilicon |
| R2-2402830 |
Clarification on plmn-IdentityIndex-r16 in SIB3 and SIB4 |
Huawei, HiSilicon |
| R2-2402923 |
Clarification on SIB1 reception for ETWS/CMAS |
Samsung |
| R2-2402935 |
Clarification on UE behaviour for context retrieval during handover failure |
Samsung R&D Institute UK |
| R2-2403171 |
Dummy the rrc-TransactionIdentifier field from IABOtherInformation |
Ericsson |
| R2-2403172 |
Dummy the rrc-TransactionIdentifier field from IABOtherInformation |
Ericsson |
| R2-2403173 |
Dummy the rrc-TransactionIdentifier field from IABOtherInformation |
Ericsson |
| R2-2403346 |
PUCCH configuration during RRC Resume |
Qualcomm Incorporated |
| R2-2403347 |
PUCCH configuration during RRC Resume |
Qualcomm Incorporated |
| R2-2403350 |
PUCCH configuration during RRC Resume |
Qualcomm Incorporated |
| R2-2403351 |
PUCCH configuration during RRC Resume |
Qualcomm Incorporated |
| R2-2403390 |
Correction on keyToUse field value in CellGroupConfig |
Philips International B.V. |
| R2-2403391 |
Correction on keyToUse field value in CellGroupConfig |
Philips International B.V. |
| R2-2403393 |
Correction on keyToUse field value in CellGroupConfig |
Philips International B.V. |
| R2-2403395 |
Correction on keyToUse field value in CellGroupConfig |
Philips International B.V. |
| R2-2403443 |
Correction on setuprelease related procedural text in rel-16 |
Google |
| R2-2403453 |
Correction on setuprelease related procedural text in rel-17 |
Google |
| R2-2403456 |
Correction on Point A related reference in RRC spec |
Philips International B.V. |
| R2-2403457 |
Correction on Point A related reference in RRC spec |
Philips International B.V. |
| R2-2403459 |
Correction on Point A related reference in RRC spec |
Philips International B.V. |
| R2-2403460 |
Correction on Point A related reference in RRC spec |
Philips International B.V. |
| 5.1.3.2 |
UE capabilities |
|
| R2-2402662 |
Correction on prerequisite of diffNumerologyAcrossPUCCH-Group |
Huawei, HiSilicon |
| R2-2402663 |
Correction on prerequisite of diffNumerologyAcrossPUCCH-Group |
Huawei, HiSilicon |
| R2-2402664 |
Correction on prerequisite of diffNumerologyAcrossPUCCH-Group |
Huawei, HiSilicon |
| R2-2402665 |
Correction on prerequisite of diffNumerologyAcrossPUCCH-Group |
Huawei, HiSilicon |
| R2-2402955 |
Discussion on UE capabilities for two PUCCH groups |
Qualcomm Incorporated |
| R2-2402956 |
Correction on prerequisite feature for csi-ReportingCrossPUCCH-Grp-r16 |
Qualcomm Incorporated |
| R2-2402957 |
Correction on prerequisite feature for csi-ReportingCrossPUCCH-Grp-r16 |
Qualcomm Incorporated |
| R2-2402958 |
Correction on prerequisite feature for csi-ReportingCrossPUCCH-Grp-r16 |
Qualcomm Incorporated |
| R2-2403432 |
Clarification on the Supported Bandwidth of the PUSCH-less Cell |
ZTE Corporation, Sanechips |
| 5.3 |
NR Positioning Support |
|
| R2-2402455 |
Correction to on-demand SIB request for RTK |
Huawei, HiSilicon |
| R2-2402456 |
Correction to on-demand SIB request for RTK |
Huawei, HiSilicon |
| R2-2402457 |
Correction to on-demand SIB request for RTK |
Huawei, HiSilicon |
| R2-2403524 |
Missing Conditionally mandatory features without UE radio access capability parameters for 80ms scheduling offset for positioning SI acquisition |
Ericsson |
| R2-2403527 |
RIL E138 SBAS-ID Field Description Correction |
Ericsson, ZTE Corporation |
| R2-2403528 |
SBAS-ID Field Description Correction |
Ericsson, ZTE Corporation |
| R2-2403553 |
Missing Conditionally mandatory features without UE radio access capability parameters for 80ms scheduling offset for positioning SI acquisition |
Ericsson |
| R2-2403558 |
Missing Conditionally mandatory features without UE radio access capability parameters for 80ms scheduling offset for positioning SI acquisition |
Ericsson |
| R2-2403559 |
RIL E138 SBAS-ID Field Description Correction |
Ericsson, ZTE Corporation |
| R2-2403700 |
Correction to on-demand SIB request |
Huawei, HiSilicon, Ericsson |
| R2-2403701 |
Correction to on-demand SIB request |
Huawei, HiSilicon, Ericsson |
| R2-2403702 |
Correction to on-demand SIB request |
Huawei, HiSilicon |
| R2-2403797 |
Missing Conditionally mandatory features without UE radio access capability parameters for 80ms scheduling offset for positioning SI acquisition |
Ericsson |
| R2-2403798 |
Missing Conditionally mandatory features without UE radio access capability parameters for 80ms scheduling offset for positioning SI acquisition |
Ericsson |
| R2-2403799 |
Missing Conditionally mandatory features without UE radio access capability parameters for 80ms scheduling offset for positioning SI acquisition |
Ericsson |
| R2-2403804 |
RIL E138 SBAS-ID Field Description Correction |
Ericsson, ZTE Corporation |
| R2-2403805 |
SBAS-ID Field Description Correction |
Ericsson, ZTE Corporation |
| R2-2403806 |
RIL E138 SBAS-ID Field Description Correction |
Ericsson, ZTE Corporation |
| 6.1 |
Common |
|
| R2-2403239 |
Logging RLF report after a successful fast MCG recovery |
Ericsson |
| R2-2403240 |
Mirror CR on Logging RLF report after a successful fast MCG recovery |
Ericsson |
| 6.1.1 |
Stage 2 and Organisational |
|
| R2-2402125 |
Reply LS on the service requirement of restricting satellite access RAT type (R3-241204; contact: Ericsson) |
RAN3 |
| R2-2402145 |
Reply LS on user consent for SON/MDT for NB-IoT UEs (S5-238102; contact: Ericsson) |
SA5 |
| 6.1.2 |
User Plane corrections |
|
| R2-2402872 |
Clarification on HARQ RTT Timer operation |
Apple, Nokia, Nokia Shanghai Bell |
| R2-2402873 |
MAC clarificaiton on HARQ RTT Timer operation |
Apple |
| R2-2402874 |
Clarification on HARQ RTT Timer operation |
Apple |
| R2-2402964 |
The remaining issue of restarting the HARQ RTT Timer |
LG Electronics Inc. |
| R2-2402985 |
Support of flexible number of TCI state activation |
Samsung |
| R2-2402986 |
Support of flexible number of TCI state activation |
Samsung |
| R2-2403343 |
Correction on multicast DRX to support NTN |
LG Electronics Inc. |
| R2-2403344 |
Correction on multicast DRX to support NTN |
LG Electronics Inc. |
| R2-2403379 |
Clarification on PHR and PHR MAC CE for feMIMO |
ZTE Corporation,Sanechips |
| R2-2403380 |
Corrections to PHR for PUSCH repetition with mTRP |
ZTE Corporation, Sanechips |
| R2-2403381 |
Corrections to PHR for PUSCH repetition with mTRP |
ZTE Corporation, Sanechips |
| R2-2403410 |
The remaining issue of restarting the HARQ RTT Timer |
LG Electronics Inc. |
| R2-2403685 |
Correction on RACH resource set availability check |
vivo, Guangdong Genius |
| R2-2403686 |
Correction on RACH resource set availability check |
vivo, Guangdong Genius |
| R2-2403968 |
LS on type 3 PH value for the serving cell configured with mTRP |
RAN2 |
| R2-2403986 |
Correction on RACH resource set availability check |
vivo, Guangdong Genius |
| R2-2403987 |
Correction on RACH resource set availability check |
vivo, Guangdong Genius |
| 6.1.3.1 |
NR RRC |
|
| R2-2402183 |
Correction on Redcap 1 Rx and 2 Rx barring |
OPPO |
| R2-2402184 |
Correction on (e)Redcap 1 Rx and 2 Rx barring |
OPPO |
| R2-2402238 |
CEF and RLF reporting for RedCap UEs |
MediaTek Inc., Qualcomm Incorporated, Nordic Semiconductor ASA, Ericsson |
| R2-2402239 |
CEF and RLF reporting for (e)RedCap UEs |
MediaTek Inc., Qualcomm Incorporated, Nordic Semiconductor ASA, Ericsson |
| R2-2402240 |
CEF and RLF reporting for RedCap UEs |
MediaTek Inc., Qualcomm Incorporated, Nordic Semiconductor ASA, Ericsson |
| R2-2402241 |
CEF and RLF reporting for (e)RedCap UEs |
MediaTek Inc., Qualcomm Incorporated, Nordic Semiconductor ASA, Ericsson |
| R2-2402243 |
CR to 38.331 on supporting paging monitoring for ongoing SDT |
MediaTek Inc. |
| R2-2402244 |
CR to 38.331 on supporting paging monitoring for ongoing SDT |
MediaTek Inc. |
| R2-2402245 |
CR to 38.306 on supporting paging monitoring for ongoing SDT |
MediaTek Inc. |
| R2-2402293 |
Correction to PDCP configuration for multicast MRB |
MediaTek Inc. |
| R2-2402294 |
Correction to PDCP configuration for multicast MRB |
MediaTek inc. |
| R2-2402358 |
Clarification on rsrp-ThresholdMsg3 |
Huawei, HiSilicon |
| R2-2402480 |
CR to 38.331 on supporting paging monitoring for ongoing SDT |
MediaTek Inc. |
| R2-2402520 |
Further considerations on periodicity of TRS resources for idle/inactive UEs |
CATT |
| R2-2402521 |
Correction on TRS for idle and inactive UEs |
CATT |
| R2-2402522 |
Correction on TRS for idle and inactive UEs |
CATT |
| R2-2402523 |
Correction on TRS for idle and inactive UEs |
CATT |
| R2-2402591 |
Missing measurement gap applicability description for NCSG |
OnePlus |
| R2-2402607 |
Missing measurement gap applicability description for NCSG |
OPPO |
| R2-2402616 |
Discussion on FeatureCombinationPreambles for RedCap |
vivo, Guangdong Genius |
| R2-2402617 |
Correction on FeatureCombinationPreambles for RedCap |
vivo, Guangdong Genius |
| R2-2402618 |
Correction on FeatureCombinationPreambles for RedCap |
vivo, Guangdong Genius |
| R2-2402640 |
Add abbreviation for GSO in 38.331 |
ZTE Corporation, Sanechips |
| R2-2402641 |
Add abbreviation for GSO in 38.331 |
ZTE Corporation, Sanechips |
| R2-2402739 |
Discussion on eDRX system information change indication |
Nokia |
| R2-2402740 |
Correction on eDRX system information change indication |
Nokia |
| R2-2402741 |
Correction on eDRX system information change indication |
Nokia |
| R2-2402777 |
Prioritization of SDT unicast over MBS broadcast |
Samsung, Ericsson |
| R2-2402778 |
Clarification on multicast MRBs during SDT configuration |
Samsung |
| R2-2402922 |
Clarification on codebook types in UE capability enquiry |
Samsung |
| R2-2403076 |
Correction on the target cell information in intra-RAT SHR |
ZTE Corporation, Sanechips |
| R2-2403077 |
Correction on the target cell information in intra-RAT SHR |
ZTE Corporation, Sanechips |
| R2-2403155 |
Discussion on QoE session status handling during CHO |
Huawei, HiSilicon |
| R2-2403250 |
Correction CR for QoE measurements and conditional handover |
Ericsson |
| R2-2403251 |
Correction CR for QoE measurements and conditional handover |
Ericsson, China Unicom |
| R2-2403258 |
Corrections to description of rach-OccasionsSI for SI request |
Samsung |
| R2-2403268 |
Correction on RedCap 1 Rx and 2 Rx barring |
Nokia |
| R2-2403269 |
Correction on (e)Redcap 1 Rx and 2 Rx barring |
Nokia |
| R2-2403278 |
Corrections to description of rach-OccasionsSI for SI request |
Samsung Electronics Co., Ltd |
| R2-2403331 |
Miscellaneous non-controversial corrections Set XXII |
Ericsson |
| R2-2403389 |
Clarification to SIB2 processing when SUL is not configured on serving cell |
Qualcomm Incorporated |
| R2-2403392 |
Missing measurement gap applicability description for NCSG |
OPPO |
| R2-2403396 |
Clarification to SIB2 processing when SUL is not configured on serving cell |
Qualcomm |
| R2-2403465 |
Correction on successful handover report configuration |
Samsung |
| R2-2403542 |
Clarification on TRS in idle and inactive |
Ericsson, MediaTek, ZTE, Nokia, Huawei, HiSilicon, Apple |
| R2-2403543 |
Correction on TRS in idle and inactive |
Ericsson, MediaTek, ZTE, Nokia, Huawei, HiSilicon, Apple |
| R2-2403544 |
DRAFT Reply LS on periodicity of TRS resources for idle/inactive UEs |
Ericsson |
| R2-2403545 |
RLM and BFD relaxation when short DRX is configured |
Ericsson, Nokia, Qualcomm, Huawei, HiSilicon |
| R2-2403619 |
Clarification to SIB2 processing when SUL is not configured on serving cell |
Qualcomm Incorporated |
| R2-2403647 |
Clarification to SIB2 processing when SUL is not configured on serving cell |
Qualcomm Incorporated |
| R2-2403654 |
Clarification to SIB2 processing when SUL is not configured on serving cell |
Qualcomm Incorporated |
| R2-2403655 |
Clarification to SIB2 processing when SUL is not configured on serving cell |
Qualcomm Incorporated |
| R2-2403707 |
CR to 38.331 on supporting paging monitoring for ongoing SDT |
MediaTek Inc. |
| R2-2403708 |
CR to 38.331 on supporting paging monitoring for ongoing SDT |
MediaTek Inc. |
| R2-2403841 |
Correction on (e)Redcap 1 Rx and 2 Rx barring |
Nokia |
| R2-2403847 |
Correction on TRS for idle and inactive UEs |
CATT |
| R2-2403848 |
Clarification on TRS in idle and inactive |
Ericsson, MediaTek, ZTE, Nokia, Huawei, HiSilicon, Apple |
| R2-2403849 |
Correction on TRS in idle and inactive |
Ericsson, MediaTek, ZTE, Nokia, Huawei, HiSilicon, Apple |
| R2-2403851 |
Clarification RLM/BFD relaxation and short DRX |
Ericsson |
| R2-2403852 |
Clarification RLM/BFD relaxation and short DRX |
Ericsson |
| R2-2403853 |
Clarification RLM/BFD relaxation and short DRX |
Ericsson |
| R2-2403855 |
DRAFT LS on RLM and BFD relaxation when short DRX is configured |
Ericsson |
| R2-2403862 |
Clarification RLM/BFD relaxation and short DRX |
Ericsson, Nokia, Qualcomm, Huawei, HiSilicon, vivo |
| R2-2403863 |
Clarification RLM/BFD relaxation and short DRX |
Ericsson, Nokia, Qualcomm, Huawei, HiSilicon |
| R2-2403864 |
DRAFT LS on RLM and BFD relaxation when short DRX is configured |
Ericsson |
| R2-2403995 |
LS on RLM and BFD relaxation when short DRX is configured |
RAN2 |
| 6.1.3.2 |
UE capabilities |
|
| R2-2402136 |
LS on IE supportedBandwidthCombinationSetIntraENDC and IE intraBandENDC-Support (R4-2403809; contact: Google) |
RAN4 |
| R2-2402232 |
Discussion on R4-2403809 |
OPPO |
| R2-2402307 |
Support of capability indication for multiple intra-band EN-DC components in one BC |
CATT |
| R2-2402308 |
Support of capability indication for multiple intra-band EN-DC components in one BC |
CATT |
| R2-2402309 |
Support of capability indication for multiple intra-band EN-DC components in one BC |
CATT |
| R2-2402310 |
Support of capability indication for multiple intra-band EN-DC components in one BC |
CATT |
| R2-2402311 |
Support of capability indication for multiple intra-band EN-DC components in one BC |
CATT |
| R2-2402666 |
Correction on modifiedMPR-Behaviour |
Huawei, HiSilicon |
| R2-2402667 |
Correction on modifiedMPR-Behaviour |
Huawei, HiSilicon |
| R2-2402668 |
Discussion on ambiguous signaling for intra-band EN-DC (LS R4-2403809) |
Huawei, HiSilicon |
| R2-2403009 |
Correction to srs-AntennaSwitchingBeyond4RX-r17 |
Ericsson |
| R2-2403010 |
Correction to srs-AntennaSwitchingBeyond4RX-r17 |
Ericsson |
| R2-2403144 |
Internode signalling for UE maximum aggregated BW capability |
Ericsson |
| R2-2403433 |
Clarification on the srs-AntennaSwitchingBeyond4RX-r17 |
ZTE Corporation, Sanechips |
| R2-2403434 |
Clarification on the srs-AntennaSwitchingBeyond4RX-r17 |
ZTE Corporation, Sanechips |
| R2-2403435 |
Consideration on the Aggragated Bandwidth for the NR-DC |
ZTE Corporation, Sanechips |
| R2-2403436 |
Introduction of Inter-node Coordination on the Aggregated Bandwidth for the NR-DC (r17) |
ZTE Corporation, Sanechips |
| R2-2403437 |
Introduction of Inter-node Coordination on the Aggregated Bandwidth for the NR-DC (r18) |
ZTE Corporation, Sanechips |
| R2-2403438 |
Correction on the supportedBandwidthDL/UL-v1780 for the NR-DC (r17) |
ZTE Corporation, Sanechips |
| R2-2403439 |
Correction on the supportedBandwidthDL/UL-v1780 for the NR-DC (r18) |
ZTE Corporation, Sanechips |
| R2-2403449 |
Inter-node signalling to support BCS5 aggregated bandwidth in NR-DC |
Nokia |
| R2-2403450 |
Correction to supportedMinBandwidth (Cat F) |
Nokia |
| R2-2403451 |
Correction to supportedMinBandwidth |
Nokia |
| R2-2403466 |
Clarification on usage of LEO or NGSO |
MediaTek Inc. |
| R2-2403467 |
Clarification on usage of LEO or NGSO |
MediaTek Inc. |
| R2-2403468 |
Clarification on usage of LEO or NGSO |
MediaTek Inc. |
| R2-2403470 |
Clarification on usage of LEO or NGSO |
MediaTek Inc. |
| R2-2403471 |
LS on usage of LEO or NGSO |
MediaTek Inc. |
| R2-2403507 |
Discussion on supportedBandwidthCombinationSetIntraENDC and intraBandENDC-Support |
Google Inc. |
| R2-2403510 |
Introduction of new intra-band EN-DC capabilities for inter-band EN-DC |
Google Inc. |
| R2-2403515 |
Introduction of new intra-band EN-DC capabilities for inter-band EN-DC |
Google Inc. |
| R2-2403518 |
Introduction of new intra-band EN-DC capabilities for inter-band EN-DC |
Google Inc. |
| R2-2403523 |
Introduction of new intra-band EN-DC capabilities for inter-band EN-DC |
Google Inc. |
| R2-2403842 |
Introduction of new intra-band EN-DC capabilities for inter-band EN-DC |
Google Inc. |
| R2-2403843 |
Introduction of new intra-band EN-DC capabilities for inter-band EN-DC |
Google Inc. |
| R2-2403844 |
Introduction of new intra-band EN-DC capabilities for inter-band EN-DC |
Google Inc. |
| R2-2403845 |
Introduction of new intra-band EN-DC capabilities for inter-band EN-DC |
Google Inc. |
| R2-2403846 |
Summary of [AT125bis][752][Maint] Ambiguous signaling for intra-band EN-DC (Google) |
Google |
| R2-2403858 |
LS on usage of LEO or NGSO |
RAN2 |
| R2-2403983 |
Introduction of Inter-node Coordination on the Aggregated Bandwidth for the NR-DC (r17) |
ZTE Corporation, Sanechips |
| R2-2403984 |
Introduction of Inter-node Coordination on the Aggregated Bandwidth for the NR-DC (r18) |
ZTE Corporation, Sanechips |
| 6.2 |
NR Sidelink relay |
|
| R2-2402513 |
Clarification on the Remote UE behaviour on short message monitoring |
CATT |
| R2-2402514 |
Clarification on the Remote UE behaviour on short message monitoring |
CATT |
| R2-2402678 |
Miscellaneous RRC corrections for Rel-17 SL relay |
Huawei, HiSilicon |
| R2-2402679 |
Miscellaneous RRC corrections for SL relay |
Huawei, HiSilicon |
| R2-2403309 |
SRAP-related corrections to 38.300 |
Samsung |
| R2-2403310 |
SRAP-related corrections to 38.300 |
Samsung |
| R2-2403398 |
Correction on SidelinkUEInformationNR |
Philips International B.V. |
| R2-2403400 |
Correction on SidelinkUEInformationNR |
Philips International B.V. |
| R2-2403474 |
Corrections for SL relay |
ZTE, Sanechips |
| R2-2403475 |
Corrections for SL relay |
ZTE, Sanechips |
| R2-2403652 |
SRAP-related corrections to 38.300 |
Samsung |
| R2-2403800 |
Miscellaneous RRC corrections for Rel-17 SL relay |
Huawei, HiSilicon |
| R2-2403801 |
Miscellaneous RRC corrections for SL relay |
Huawei, HiSilicon |
| 6.4 |
NR positioning enhancements |
|
| R2-2402458 |
Correction on the UL TEG report |
Huawei, HiSilicon |
| R2-2402459 |
Correction on the UL TEG report |
Huawei, HiSilicon |
| R2-2403387 |
Correction on posSIB(s) acquisition [SI-SCHEDULING] |
Philips International B.V., Ericsson |
| R2-2403388 |
Correction on posSIB(s) acquisition [SI-SCHEDULING] |
Philips International B.V., Ericsson |
| R2-2403525 |
Correction of when to cancel the triggered SR for positioning measurement gap activation/deactivation |
Ericsson |
| R2-2403526 |
Correction of when to cancel the triggered SR for positioning measurement gap activation/deactivation |
Ericsson |
| R2-2403740 |
Introduction of NR UE Rx-Tx time difference measurement in NR UL E-CID |
Ericsson, Polaris Wireless, China Telecom, NTT Docomo, AT&T, FirstNet, Intel, Comtech, Nokia, Nokia Shanghai Bell, Verizon Wireless, Huawei, ZTE |
| 6.6 |
NR Sidelink enhancements |
|
| R2-2402319 |
Coexistence between SL DRX and SL IUC |
LG Electronics France |
| R2-2402851 |
Correction on coexistence between SL DRX and SL IUC |
LG Electronics Inc. |
| R2-2402853 |
Correction on coexistence between SL DRX and SL IUC |
LG Electronics Inc. |
| R2-2402944 |
Correction to the IUC based resource selection |
Ericsson |
| R2-2402945 |
Correction to the IUC based resource selection |
Ericsson |
| R2-2403584 |
Correction on tx profile for SL DRX |
ZTE Corporation, Sanechips |
| R2-2403585 |
Correction on tx profile for SL DRX |
ZTE Corporation, Sanechips |
| R2-2403921 |
Correction on tx profile for SL DRX |
ZTE Corporation, Sanechips |
| R2-2403922 |
Correction on tx profile for SL DRX |
ZTE Corporation, Sanechips |
| 7.0.1 |
UE Capabilites |
|
| R2-2402109 |
LS on Rel-18 RAN1 UE features list for NR after RAN1#116 (R1-2401711; contact: NTT DOCOMO, AT&T) |
RAN1 |
| R2-2402132 |
LS on RAN4 UE feature list for Rel-18 (version 3) (R4-2403636; contact: CMCC) |
RAN4 |
| R2-2402231 |
Left issues on SL-U Power Class Capability |
OPPO |
| R2-2403440 |
Correction on the srs-AntennaSwitching8T8R-r18 (38331) |
ZTE Corporation, Sanechips |
| R2-2403441 |
Correction on the srs-AntennaSwitching8T8R-r18 (38306) |
ZTE Corporation, Sanechips |
| R2-2403964 |
Correction on R18 SL-U Power Class |
OPPO |
| R2-2403965 |
Correction on R18 SL-U Power Class |
OPPO |
| 7.0.3 |
ASN.1 Review |
|
| R2-2402233 |
[O319][O320] Discussion SL-feature Co-configuration |
OPPO, Nokia, Samsung |
| R2-2402765 |
[H071] Paging collision between MBS and SDT |
Huawei, HiSilicon |
| R2-2402992 |
LTE ASN.1 Review file |
Samsung |
| R2-2402993 |
LTE RIL List |
Samsung |
| R2-2402994 |
LTE ASN.1 Class 0 Issues |
Samsung |
| R2-2403322 |
Miscellaneous corrections from ASN.1 review Q2 |
Ericsson |
| R2-2403323 |
RIL List for MULTI/Gen issues |
Ericsson |
| R2-2403326 |
MULTI/GEN Exxx RILs |
Ericsson |
| R2-2403327 |
NR ASN.1 Q2 Class 0 Issues |
Ericsson |
| R2-2403328 |
NR ASN.1 Q2 Review file |
Ericsson |
| R2-2403329 |
NR RIL List Q2 Phase 1 |
Ericsson |
| R2-2403583 |
Co-existence of different SL services |
ZTE Corporation, Sanechips |
| 7.0.4 |
RACH-less HO |
|
| R2-2402460 |
Rapporteur correction to MAC spec for RACH-less HO [RACH-lessHO] |
Huawei, HiSilicon |
| R2-2402461 |
Corrections to remaining issues for RACH-less HO for MAC spec [RACH-lessHO] |
Huawei, HiSilicon |
| R2-2402848 |
SFN reading required for RACH-less |
Xiaomi |
| R2-2402865 |
Remaining issues on RACH-less HO |
Apple |
| R2-2402917 |
Remaining MAC issues in RACH-less HO procedure |
CATT |
| R2-2403182 |
[E242] Rapporteur corrections on RRC for the generalization of RACH-less [RACH-lessHO] |
Ericsson |
| R2-2403297 |
Report of [POST125][024][RACH-less] Remaining issues – Capabilities |
Samsung, InterDigital |
| R2-2403298 |
Handling of DRX and measurement gaps during RACH-less handover |
Samsung |
| R2-2403317 |
Report of [POST125][024][RACH-less] Remaining issues - Other |
InterDigital, Samsung |
| R2-2403318 |
DRAFT LS on parameters used for CG RACH-less Handover |
InterDigital |
| R2-2403352 |
Corrections to CG-based RACH-less HO |
Samsung |
| R2-2403463 |
Remaining issue on RACH-less handover generalization in MAC |
LG Electronics Inc. |
| R2-2403588 |
RACHless HO support in release 18 |
Nokia |
| R2-2403593 |
RACHless open issues |
Nokia |
| R2-2403709 |
Discussion on remaining issues for RACH-less HO for MAC spec [RACH-lessHO] |
Huawei, HiSilicon |
| R2-2403710 |
Discussion on remaining issues for RACH-less HO for MAC spec [RACH-lessHO] |
Huawei, HiSilicon |
| R2-2403711 |
Rapporteur correction to MAC spec for RACH-less HO [RACH-lessHO] |
Huawei, HiSilicon |
| R2-2403993 |
[DRAFT] LS on parameters used for CG RACH-less Handover |
InterDigital |
| R2-2403996 |
LS on parameters used for CG RACH-less Handover |
RAN2 |
| 7.0.5 |
Other |
|
| R2-2402331 |
Discussion on SL-U and SL-CA co-existence with SL-PRS transmission and A2X communication |
vivo |
| R2-2402462 |
Correction on RACH resource set selection for CFRA |
Huawei, HiSilicon |
| R2-2402463 |
Discussion on the co-existence of R18 SL enhancements |
Huawei, HiSilicon |
| R2-2402464 |
Guideline for late non-critical extension [lateNonCriticalExt] |
Huawei, HiSilicon |
| R2-2403038 |
Miscellaneous corrections |
Samsung (Rapporteur) |
| R2-2403039 |
Miscellaneous corrections |
Samsung (Rapporteur) |
| R2-2403040 |
Miscellaneous corrections |
Samsung (Rapporteur) |
| R2-2403330 |
Draft LS on ASN1 names in RAN1 parameter list |
Ericsson |
| R2-2403364 |
Correcting Figures |
Nokia (Rapporteur) |
| R2-2403642 |
Correction on RACH resource set selection for CFRA |
Huawei, HiSilicon |
| 7.1 |
NR network-controlled repeaters |
|
| R2-2403316 |
Correction to BFR for NCR |
Samsung |
| R2-2403981 |
Report from [AT125bis][002][NCR] All NCR corrections tdocs (Apple) |
Apple |
| 7.1.1 |
Organizational |
|
| R2-2403627 |
Clarification to Network-Controlled Repeaters Stage-2 description |
Ericsson, Nokia |
| R2-2403730 |
RILs conclusion for NCR |
ZTE Corporation (rapporteur) |
| R2-2403970 |
Clarification to Network-Controlled Repeaters Stage-2 description |
Ericsson, Nokia |
| 7.1.2 |
Others |
|
| R2-2403445 |
Correction to P-Max and NS value usage for NCR-MT |
Nokia |
| R2-2403446 |
Discussion on P-Max and NS value handling for NCR-MT |
Nokia |
| 7.2.1 |
Organizational |
|
| R2-2402106 |
Reply LS on MAC agreements for SL Positioning (R1-2401552; contact: Intel) |
RAN1 |
| R2-2402108 |
LS on bandwidth aggregation for positioning (R1-2401708; contact: ZTE) |
RAN1 |
| R2-2402118 |
LS on the bandwidth used in measurements for positioning of RedCap UEs (R1-2401801; contact: Ericsson) |
RAN1 |
| R2-2402121 |
LS on higher layer parameters for SL Positioning (R1-2401827; contact: Intel, Qualcomm) |
RAN1 |
| R2-2402127 |
Updates on measurement report mapping for Positioning Enhancements WI (R4-2403363; contact: Huawei) |
RAN4 |
| R2-2402133 |
LS on SRS and PRS bandwidth aggregation feature for positioning (R4-2403654; contact: Ericsson) |
RAN4 |
| R2-2402141 |
Reply LS on UE selection for Ranging_SL (S2-2403682; contact: Qualcomm) |
SA2 |
| R2-2402255 |
LPP RIL list for Rel-18 Positioning |
CATT |
| R2-2402256 |
Corrections to TS 37.355 |
CATT |
| R2-2402257 |
Leftover Issues on LPP |
CATT |
| R2-2402258 |
Questions on PRS and SRS bandwidth aggregation |
CATT |
| R2-2403532 |
Bandwidth used in measurements for positioning of RedCap Ues |
Ericsson |
| R2-2403533 |
Open issues list For RRC Positioning |
Ericsson |
| R2-2403536 |
On SRS and PRS bandwidth aggregation feature for positioning |
Ericsson |
| R2-2403537 |
Miscellaneous RRC Positioning Corrections |
Ericsson |
| R2-2403721 |
LPP RIL list for Rel-18 Positioning |
CATT |
| R2-2403796 |
[AT125bis][401][POS] PRU terminology in LPP (CATT) |
CATT |
| R2-2403807 |
LS to RAN1 on bandwidth aggregation |
RAN2 |
| R2-2403818 |
Corrections to TS 37.355 |
CATT |
| R2-2403819 |
Miscellaneous and RRC Positioning RILs based Corrections |
Ericsson |
| R2-2403971 |
Miscellaneous corrections on 38.331 for Rel-18 positioning UE capabilities |
Xiaomi |
| R2-2403972 |
Miscellaneous corrections on 38.306 for Rel-18 positioning UE capabilities |
Xiaomi |
| R2-2403977 |
CR 38.355 for SLPP capability |
Xiaomi |
| R2-2403978 |
Miscellaneous corrections on LPP for Rel-18 positioning UE capabilities |
Xiaomi |
| R2-2404032 |
[Post125bis][408][POS] Rel-18 positioning RRC CR (Ericsson) |
Ericsson |
| 7.2.2 |
Stage 2 |
|
| R2-2402469 |
Correction to TS 38300 for R18 SL positioning |
Huawei, HiSilicon |
| R2-2402470 |
Correction to TS 38305 for R18 positioning |
Huawei, HiSilicon |
| R2-2402646 |
Discussion on remaining corrections in stage-2 |
ZTE Corporation |
| R2-2403188 |
Miscellaneous Stage 2 Corrections |
Qualcomm Incorporated |
| R2-2403500 |
Further clarifications for Positioning in RRC_INACTIVE state |
Nokia |
| R2-2403535 |
Text Proposal for Stage2 TS 38.305 |
Ericsson |
| R2-2403625 |
Correction to TS 38300 for SL positioning |
Huawei, HiSilicon |
| 7.2.3 |
SLPP corrections |
|
| R2-2402414 |
[Post125][407][POS] 38.355 updated Open Issue list |
Intel Corporation |
| R2-2402415 |
Further considerations on SLPP open issues |
Intel Corporation |
| R2-2402416 |
Miscellaneous corrections to SLPP specification |
Intel Corporation |
| R2-2402465 |
Discussion on the remaining issues for R18 SLPP |
Huawei, HiSilicon |
| R2-2402517 |
Discussion on the necessity of including the server UE positioning method in the discovery message |
OPPO, LG |
| R2-2402555 |
Correction on the maximum number of SL-PRS resource ID in ARP info |
vivo |
| R2-2402647 |
Discussion on remaining corrections in SLPP |
ZTE Corporation |
| R2-2402707 |
Discussion on SLPP open issues |
Xiaomi |
| R2-2402792 |
Discussion on error messaging in SLPP |
Lenovo |
| R2-2402899 |
Miscellaneous SLPP corrections |
Apple |
| R2-2402937 |
Further discussion on anchor UE selection |
LG Electronics Inc. |
| R2-2403189 |
Remaining issues for SLPP |
Qualcomm Incorporated |
| R2-2403231 |
Inclusion of the Server UE Positioning Method in the Discovery Message |
CEWiT |
| R2-2403261 |
[H016][ZTE004][A006] SLPP corrections |
Nokia |
| R2-2403424 |
Remaining issues on SLPP |
Samsung |
| R2-2403534 |
Discussion on SLPP RIL issues |
Ericsson |
| R2-2403541 |
SLPP RIL Issue |
Ericsson |
| R2-2403809 |
LS on application layer ID |
RAN2 |
| R2-2403810 |
LS to RAN1 on SLPP agreements |
RAN2 |
| R2-2403811 |
[AT125bis][409][POS] Remaining SLPP issues (Intel) |
Intel Corporation |
| R2-2403817 |
Miscellaneous corrections to SLPP specification |
Intel Corporation |
| 7.2.4 |
LPP corrections |
|
| R2-2402259 |
Discussion on measurement report for the bandwidth aggregation |
CATT |
| R2-2402466 |
Discussion on the remaining issues for R18 LPP |
Huawei, HiSilicon |
| R2-2402556 |
Correction on RSCP measurement info in PRU DL info |
vivo |
| R2-2402648 |
Discussion on remaining corrections in LPP |
ZTE Corporation |
| R2-2402998 |
LPP Stage 3 Open Issue - CPP |
Lenovo |
| R2-2403190 |
[RILs Q014 Q019, Q024, Q028] LPP Corrections |
Qualcomm Incorporated |
| R2-2403191 |
LPP Open Issues: PRU Operation and DL-PRS–DRX Alignment |
Qualcomm Incorporated |
| R2-2403501 |
Corrections to NR-PRU-DL-Info IE |
Nokia |
| R2-2403502 |
Request for carrier phase measurement or joint measurement and clarification for time window configuration |
Nokia |
| R2-2403540 |
LPP RIL issue |
Ericsson |
| R2-2403808 |
[AT125bis][406][POS] Remaining LPP ASN.1 proposals (CATT) |
CATT |
| R2-2403812 |
RAT-dep Integrity TRP/ARP error source correlation time correction |
Ericsson |
| R2-2403979 |
LS on DL-AoD measurements in NR-PRU-DL-Info forwarded to target UE |
RAN2 |
| 7.2.5 |
RRC corrections |
|
| R2-2402260 |
Activation of SP SRS When Configured with Validity Area |
CATT |
| R2-2402261 |
Discussion on the release of SRS configuration |
CATT, Samsung, LG Electronics Inc, Xiaomi |
| R2-2402333 |
Discussion on remaining RRC issues on the positioning |
OPPO |
| R2-2402417 |
[I166-I171] Further considerations on parameters in SUI and UAI |
Intel Corporation |
| R2-2402468 |
Discussion on RRC for R18 POS [H905][H906][H914][H916][H919] |
Huawei, HiSilicon |
| R2-2402557 |
Discussion on SUI Content for Sidelink Positioning |
vivo |
| R2-2402558 |
RRC correction for UE not supporting sidelink positioning in limited service state in 5GS |
vivo |
| R2-2402649 |
Discussion on remaining corrections in RRC |
ZTE Corporation |
| R2-2402832 |
Discussion on the remaining issues for the SRS with validity area |
Xiaomi |
| R2-2403194 |
Remaining issues for pre-configured SRS |
Qualcomm Incorporated |
| R2-2403416 |
[S208][S209][S210] Remaining issues on RRC |
Samsung |
| R2-2403530 |
RRC Positioning RIL List |
Ericsson |
| R2-2403718 |
[X041] Correction on SL-PRS-QoS-Info |
Beijing Xiaomi Mobile Software |
| R2-2403791 |
RRC Positioning RIL List |
Ericsson |
| R2-2403795 |
RRC Positioning RIL List |
Ericsson |
| 7.2.6 |
MAC corrections |
|
| R2-2402262 |
Discussion on the remaining issues on bandwidth aggregation for SRS |
CATT |
| R2-2402334 |
Discussion on RAN1 reply LS on SL-PRS transmission |
OPPO |
| R2-2402467 |
Rapporteur MAC CR for R18 positioning |
Huawei, HiSilicon |
| R2-2402471 |
Discussion on the remaining issues for MAC for R18 positioning |
Huawei, HiSilicon |
| R2-2402577 |
Discussion on SL-PRS |
ASUSTeK |
| R2-2402650 |
Discussion on remaining corrections in MAC |
ZTE Corporation |
| R2-2402706 |
Discussion on SL positioning MAC open issues |
Xiaomi |
| R2-2403201 |
MAC CE for activation/deactivation of aggregated SP SRS for positioning |
Qualcomm Incorporated |
| R2-2403341 |
Discussion on remaining MAC issues for SL positioning |
InterDigital, Inc. |
| R2-2403417 |
Remaining issues on MAC |
Samsung |
| R2-2403531 |
Addressing MAC open issues |
Ericsson |
| R2-2403820 |
Rapporteur MAC CR for R18 positioning |
Huawei, HiSilicon |
| 7.2.7 |
UE capabilities |
|
| R2-2402321 |
Compatibility between Redcap positioning feature and other R18 positioning features |
CATT |
| R2-2402578 |
Correction on UE capability regarding SL PRS |
ASUSTeK |
| 7.3.1 |
Organizational |
|
| R2-2402119 |
LS on Network Energy Savings (R1-2401810; contact: Intel, Huawei) |
RAN1 |
| R2-2402566 |
Discussion on UE capabilities for inter-band SSB-less SCell |
vivo |
| R2-2402567 |
Correction on UE capabilities for inter-band SSB-less SCell |
vivo |
| R2-2402781 |
Network energy savings for NR miscellaneous RRC CR |
Huawei, HiSilicon |
| R2-2402856 |
(Draft) Reply LS on handling repetition of PUCCH in Cell DRX |
Apple |
| R2-2403267 |
Network energy savings for NR miscellaneous MAC CR |
InterDigital |
| R2-2403704 |
NES WI RIL list |
Huawei, HiSilicon |
| R2-2403954 |
Correction on UE capabilities for inter-band SSB-less SCell |
vivo |
| R2-2403998 |
Network energy savings for NR miscellaneous RRC CR |
Huawei, HiSilicon |
| 7.3.2 |
User Plane |
|
| R2-2402160 |
Clarifications on emergency service handling under cell DTRX |
Xiaomi |
| R2-2402596 |
Coexistence of Cell DTXDRX and RACH-less LTM and handover |
Sharp |
| R2-2402656 |
Discussion on remaining issues for the emergency call |
CATT |
| R2-2402657 |
The correction on MAC spec in NES |
CATT |
| R2-2402779 |
Discussion on capturing RAN1 agreements regarding repetitions for cell DTX/DRX in the MAC specification |
Huawei, HiSilicon |
| R2-2402855 |
Remaining user plane open issues on NES |
Apple |
| R2-2403008 |
Remaining MAC aspects for cell DTX-DRX |
Ericsson |
| R2-2403127 |
Coexistence of Cell DTX DRX and RACH-less LTM |
OPPO |
| R2-2403128 |
Discussion on cell DTX DRX based on RAN1 LS |
OPPO |
| R2-2403266 |
Remaining issues on Cell DTX/DRX |
InterDigital, Nokia, Nokia Shanghai Bell |
| R2-2403356 |
Remaining issues on cell DTX and cell DRX mechanism |
LG Electronics Inc. |
| R2-2403386 |
Remaining UP issues on Cell DTX/DRX |
Samsung |
| R2-2403615 |
Capturing RAN1 agreements on handling of transmission and reception of channels during Cell DTX and DRX |
ZTE Corporation, Sanechips |
| 7.3.3 |
Control Plane corrections |
|
| R2-2402161 |
Clarifications on SSB-less SCell configuration for R15 or R18 case |
Xiaomi |
| R2-2402636 |
Clarification on configuration of the condEventA4 in NES |
ZTE Corporation, Sanechips |
| R2-2402780 |
[H080] [H081] Corrections to CSI-ReportSubConfig based on RAN1 parameter list |
Huawei, HiSilicon |
| R2-2402822 |
UE capability for SSB-less Scell |
Huawei, HiSilicon |
| R2-2402854 |
Remaining control plane open issues on NES |
Apple |
| R2-2402932 |
NES CP Corrections |
Samsung |
| R2-2403185 |
Discussion on CHO for Rel-18 NES |
Ericsson |
| R2-2403342 |
RRC CR to resolve issues on NES mode indication |
Lenovo |
| R2-2403345 |
RRC CR to resolve issues on NES mode indication |
Lenovo, NEC, CEWiT, Continental Automotive, Google |
| R2-2403594 |
Distinguishing CHO for Cell DTX/DRX or Cell off |
Nokia, Nokia Shanghai Bell |
| R2-2403595 |
Details of subconfiguration |
Nokia |
| R2-2403646 |
Clarification on NES CHO triggering and measurements |
LG Electronics Inc. |
| 7.4.1 |
Organizational |
|
| R2-2402117 |
LS on TCI state after cell switch command for LTM ( R1-2401785; contact: Fujitsu) |
RAN1 |
| R2-2402131 |
LS on R18 mobility - Improvement on SCell/SCG setup delay (R4-2403549; contact: Apple) |
RAN4 |
| R2-2403174 |
Miscellaneous corrections on further mobility enhancements in NR |
Ericsson |
| R2-2403175 |
RILs conclusions for feMob |
Ericsson |
| R2-2403176 |
Discussion on RILs conclusion Mobillity |
Ericsson |
| 7.4.2 |
Stage-2 Corrections |
|
| R2-2402747 |
Miscellaneous corrections for mobility enhancements in TS 37.340 |
ZTE Corporation |
| R2-2402995 |
Misc corrections on LTM |
MediaTek Inc., Ericsson |
| R2-2404003 |
Miscellaneous corrections for mobility enhancements in TS 37.340 |
ZTE Corporation |
| R2-2404009 |
Stage-2 corrections on LTM |
Mediatek Inc. |
| 7.4.3.1 |
L1L2 Triggered Mobility |
|
| R2-2402234 |
[E068] On SecurityConfig for LTM |
MediaTek Inc. |
| R2-2402235 |
Fast Recovery with LTM Candidates |
MediaTek Inc. |
| R2-2402236 |
LTM and MIMO 2TA |
MediaTek Inc. |
| R2-2402265 |
[F013-015] [F031-033] Corrections to TS 38.331 on LTM |
Fujitsu |
| R2-2402436 |
Discussion on RRC issues for LTM |
OPPO |
| R2-2402439 |
Discussion on cross-feature issues for LTM |
OPPO |
| R2-2402498 |
[C127][C128][C129] RRC Issues on LTM |
CATT |
| R2-2402499 |
[E074][E068] On Postponed RRC Issues |
CATT |
| R2-2402609 |
Discussion on the LTM fast recovery after RLF triggered by maximum number of RLC retransmissions |
vivo |
| R2-2402610 |
Discussion on the impact of s-Measure on L1 measurement discussion |
vivo |
| R2-2402723 |
Fallback for RACH-less LTM |
Lenovo |
| R2-2402744 |
Discussion on remaining issues for LTM |
ZTE Corporation |
| R2-2402846 |
Remaining coexistence issue for LTM |
Xiaomi |
| R2-2402905 |
Handling the transaction ID issue with LTM |
Apple |
| R2-2402921 |
Discussion on TAT expiry during LTM execution |
Samsung |
| R2-2402996 |
RRC signaling related TCI state configurations |
Panasonic |
| R2-2403032 |
Clarification on handling of conditional reconfiguration upon LTM-based recovery |
LG Electronics |
| R2-2403177 |
[E068][E231][E074][E240][S792][E236][E235] Resolution of remaining RILs for LTM |
Ericsson |
| R2-2403178 |
Co-existance of LTM with NES, NR-U, and other features |
Ericsson |
| R2-2403187 |
Control plane centric issues for LTM |
Langbo |
| R2-2403263 |
Indication of the LTM configuration ID by the UE |
Apple |
| R2-2403279 |
Remaining Co-existence Aspects of LTM with L3 Mobility and DC |
Nokia |
| R2-2403284 |
[H091][H092][H093][E068][H094][H095][H096] RRC remaining issues for LTM |
Huawei, HiSilicon |
| R2-2403299 |
On Reference Configuration [N133] and Early Processing of LTM candidates in Rel-18 |
Nokia |
| R2-2403308 |
On Mobility RILs [E068] and [S792] |
Nokia |
| R2-2403374 |
On Support 2TA For LTM Candidate |
ZTE Corporation, Sanechips |
| R2-2403454 |
[G125] Discussion on LTM cell switch execution during fast MCG recovery procedure |
Google Inc. |
| R2-2403493 |
Discussion on SCG LTM while MCG failure recovery |
Xiaomi |
| R2-2403513 |
Rel-18 L1/L2 triggered mobility remaining issues |
Sharp |
| R2-2403519 |
[F034][F035] Further issues on state variable continuation at fast LTM recovery |
Fujitsu |
| R2-2403653 |
[S792] SRB3 release during SCPAC and LTM |
Samsung |
| R2-2403712 |
[B120][B121]coexistence of LTM and conditional reconfiguration |
Lenovo |
| 7.4.3.2 |
Conditional Mobility |
|
| R2-2402500 |
[C126] RRC Issue on CHO with SCGs |
CATT |
| R2-2402501 |
[C144][C145][C146][C130][C147] RRC Issues on SCPAC |
CATT |
| R2-2402611 |
Discussion on simultaneous evaluation for both condRRCReconfig and condExecutionCondSCG |
vivo |
| R2-2402745 |
Discussion on inter-node RRC message for intra-SN SCPAC in MN format |
ZTE Corporation |
| R2-2402931 |
Considerations on CHO with SCG(s) and Subsequent CPAC |
Samsung R&D Institute UK |
| R2-2402967 |
Discussion on remaining issues of L2 reset for SCPAC |
NEC |
| R2-2403145 |
RIL-N091 and other remaining open issues for SCPAC |
Nokia |
| R2-2403252 |
Open issues for subsequent CPAC |
Ericsson |
| R2-2403285 |
[H083][H084][H085][H087][H097][H114] Remaining issues for subsequent CPAC |
Huawei, HiSilicon |
| R2-2403697 |
[O203] Issue on RRCReconfigurationComplete message delivery for intra-SN SCPAC |
OPPO (chongqing) Intelligence |
| R2-2403990 |
LS on inter-node RRC message for intra-SN SCPAC in MN format |
RAN2 |
| R2-2403991 |
TP on inter-node RRC message for intra-SN SCPAC in MN format |
ZTE Corporation |
| R2-2404001 |
LS on inter-node RRC message for intra-SN SCPAC in MN format |
RAN2 |
| R2-2404002 |
TP on inter-node RRC message for intra-SN SCPAC in MN format |
ZTE Corporation |
| 7.4.3.3 |
eEMR and IMR |
|
| R2-2402328 |
Discussion on eEMR SCell setup delay |
vivo |
| R2-2402440 |
Open issues for IMR and eEMR |
OPPO |
| R2-2402746 |
Remaining issues on eEMR and IMR |
ZTE Corporation |
| R2-2403253 |
Discussion on early measurements enhancements |
Ericsson |
| R2-2403286 |
[H144][H145][H146][H147] Issues on eEMR and IMR |
Huawei, HiSilicon |
| R2-2403494 |
Discussion on eEMR and IMR |
Xiaomi |
| R2-2403596 |
[N111][N112] Discussion and TP for EMR and non-EMR |
Nokia |
| R2-2403644 |
CA-DC capability checking for Reselection Measurement Reporting |
LG Electronics Inc. |
| R2-2403720 |
[X124] Discussion on validity status |
Xiaomi |
| R2-2403969 |
[AT125bis][502][R18Mob] EMR and reselection Measurement reporting (Nokia) |
Nokia |
| R2-2404006 |
[Post125bis][513][R18Mob] Idle/Inactive and Reselection Meas Reporting CR (Nokia)) |
Nokia |
| 7.4.4 |
MAC Corrections |
|
| R2-2402266 |
Corrections to TS 38.321 on LTM |
Fujitsu |
| R2-2402366 |
MAC corrections for LTM |
Samsung Electronics Co., Ltd |
| R2-2402437 |
Discussion on remaining MAC issues for LTM |
OPPO |
| R2-2402438 |
Discussion on TCI state related issues |
OPPO |
| R2-2402502 |
MAC Issues for LTM |
CATT |
| R2-2402579 |
Discussion on fallback RACH for LTM |
ASUSTeK |
| R2-2402580 |
Discussion on LTM candidate configuration for different CGs |
ASUSTeK |
| R2-2402581 |
Discussion on UL collision with early UL synchronization in LTM |
ASUSTeK |
| R2-2402612 |
Discussion on MAC open issues for LTM |
vivo |
| R2-2402613 |
Discussion on the remaining issues for LTM with MIMO two TA |
vivo |
| R2-2402845 |
Discussion on the SFN acquisition for LTM |
Xiaomi |
| R2-2402966 |
Discussion on DRX and measurement gap enhancement for RACH-less mobility |
NEC, Huawei, HiSilicon, Xiaomi |
| R2-2402984 |
Support of Activating the Flexible Number of TCI States using Candidate Cell TCI States Activation/Deactivation MAC CE |
Samsung |
| R2-2403101 |
Discussion on RV and carrier selection for RACH-less LTM |
NEC |
| R2-2403179 |
Adding SR resources within the LTM cell switch MAC CE |
Ericsson |
| R2-2403186 |
User plane centric issues for LTM |
Langbo |
| R2-2403280 |
On the LTM Cell Switch Aspects |
Nokia |
| R2-2403287 |
Miscellaneous corrections for further mobility enhancements |
Huawei, HiSilicon |
| R2-2403288 |
MAC remaining issues for LTM |
Huawei, HiSilicon |
| R2-2403373 |
Considerations On Remaining MAC Issues For LTM |
ZTE Corporation, Sanechips |
| R2-2403464 |
Corrections for remaining issues on MAC |
LG Electronics Inc. |
| R2-2403966 |
Summary of offline discussion [503] |
Huawei, HiSilicon |
| R2-2404023 |
Miscellaneous corrections for further mobility enhancements |
Huawei, HiSilicon |
| 7.4.5 |
UE capabilities |
|
| R2-2402237 |
UE Capabilities for CHO with Candidate SCG |
MediaTek Inc. |
| R2-2402409 |
Remaining UE capability issues for feMob |
Intel Corporation |
| R2-2403180 |
[E250] Correction on capabilities for LTM |
Ericsson |
| R2-2403289 |
Discussion on LTM UE capability |
Huawei, HiSilicon |
| R2-2403495 |
Discussion on UE capabilities for Rel-18 Mobility |
Xiaomi |
| R2-2403665 |
Capabilities for PDCCH-ordered RACH |
Ericsson |
| R2-2404014 |
LS on LTM L1 intra and inter-frequency measurements |
RAN2 |
| 7.5.1 |
Organizational |
|
| R2-2402386 |
Miscellaneous correction to TS 38.321 (rapporteur’s CR) |
Qualcomm Incorporated |
| R2-2403103 |
RRC corrections for XR |
Huawei, HiSilicon |
| R2-2403104 |
RIL resolutions for XR |
Huawei, HiSilicon |
| R2-2403360 |
Miscellaneous XR Corrections |
Nokia (Rapporteur) |
| R2-2404008 |
RRC corrections for XR |
Huawei, HiSilicon |
| R2-2404036 |
RIL resolutions for XR |
Huawei, HiSilicon |
| 7.5.2 |
RRC corrections |
|
| R2-2402508 |
[C260] and Two Other Key Issues |
CATT |
| R2-2402760 |
Clarification on BAT report for XR |
ZTE Corporation, Sanechips |
| R2-2403131 |
[O502] Discussion on time-domain resource allocation for multi-PUSCH CG |
OPPO |
| 7.5.3.1 |
BSR and DSR enhancements for XR |
|
| R2-2402507 |
Further Discussion on DSR Triggering Modelling |
CATT, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R2-2402509 |
Leftover Issue on BSR |
CATT, DENSO CORPORATION, Nokia, Nokia Shanghai Bell |
| R2-2402519 |
Remaining issues for DSR and BSR |
Huawei, HiSilicon |
| R2-2402582 |
Discussion on SR configuration for DSR MAC CE |
ASUSTeK |
| R2-2402614 |
Discussion on remaining issues of BSR for XR |
vivo |
| R2-2402677 |
Remaining issues on DSR and proposed TP to MAC |
Xiaomi Communications |
| R2-2402948 |
Corrections to DSR Procedure |
Lenovo |
| R2-2403129 |
Discussion on the RA procedure termination for DSR-SR |
OPPO |
| R2-2403408 |
Clarification on SDU for DSR |
Nokia, Nokia Shanghai Bell |
| R2-2403505 |
Remaining issues on BSR and DSR |
Samsung |
| 7.5.3.2 |
PDCP and discard operation |
|
| R2-2402267 |
Discussions on PDCP SN Gap Report |
Fujitsu |
| R2-2402387 |
Issues related to PSI-based discard |
Qualcomm Incorporated |
| R2-2402759 |
Remaining aspects of PDCP report |
ZTE Corporation, Sanechips |
| R2-2402775 |
Considerations for PDCP Discard |
Samsung |
| R2-2402840 |
PSI-based discarding on split bearers |
Nokia, Nokia Shanghai Bell |
| R2-2403361 |
Triggering of PDCP SN gap report |
Nokia |
| R2-2403371 |
PDCP SN gap reporting |
LG Electronics, Ericsson |
| R2-2403414 |
PDCP SN gap reporting |
Xiaomi |
| R2-2403517 |
PDCP SN Gap Report |
MediaTek Inc. |
| R2-2403608 |
Report of [POST125][017][XR] PDCP report (Ericsson) |
Ericsson |
| R2-2403693 |
Comparison of control PDU and header-only data PDU based approaches for PDCP SN gap report |
Futurewei |
| 7.5.3.3 |
Others |
|
| R2-2402388 |
Correction to the determination of unused CG occasions |
Qualcomm Incorporated, Apple, MediaTek, Nokia, Nokia Shanghai Bell |
| R2-2402472 |
Remaining issues for DRX operations for XR |
Huawei, HiSilicon |
| R2-2402473 |
Discussion on MAC procedure for UTO-UCI |
Huawei, HiSilicon |
| R2-2402583 |
Correction on support of remapping PDU Set boundary in SDAP |
ASUSTeK |
| R2-2402615 |
Determination of Unused CG Occasions |
vivo |
| R2-2402761 |
Consideration on DRX_SFN_COUNTER for XR |
ZTE Corporation, Sanechips |
| R2-2402878 |
On Clarifications of SR Signaling and Unused CG Occasion |
Apple, Samsung |
| R2-2403046 |
Remaining issues on non-integer DRX cycle |
NEC Corporation |
| R2-2403089 |
Correction for initialization of DRX_SFN_COUNTER for XR |
ZTE Corporation, Sanechips |
| R2-2403130 |
Correction on the DRX_SFN_COUNTER initialization |
OPPO |
| R2-2403224 |
Rel-18 MAC corrections |
Ericsson |
| R2-2403367 |
R18 XR UTO-UCI and R16 enhanced UL skipping correction |
Ericsson, ZTE Corporation |
| R2-2403385 |
Clarification on Retransmission-less CG |
Samsung |
| R2-2403666 |
Discussion on determination of UTO-UCI content |
LG Electronics Inc. |
| R2-2403695 |
Correction for initialization of DRX_SFN_COUNTER for XR |
ZTE Corporation, Sanechips |
| 7.6.1 |
Organizational |
|
| R2-2402120 |
LS on Rel-18 RAN1 UE features list for LTE after RAN1#116 (R1-2401824; contact: NTT DOCOMO, AT&T) |
RAN1 |
| R2-2402143 |
Reply LS on UE Location Information for NB-IoT NTN (S2-2403851; contact: Qualcomm) |
SA2 |
| R2-2402187 |
Discussion on SA2 and CT1 reply LS on UE Location Information for NB-IoT NTN |
OPPO |
| R2-2402771 |
Discussion on the need for eNB to get UE location information from MME |
Huawei, HiSilicon |
| R2-2402813 |
Discussion on reply LS on UE Location Information for NB-IoT NTN |
Qualcomm Incorporated |
| R2-2402814 |
[Draft] Reply LS on UE Location Information for NB-IoT NTN |
Qualcomm Incorporated |
| R2-2402888 |
Discussion on LS about UE Location Information for NB-IoT NTN |
Apple |
| R2-2403210 |
Introduction of IoT NTN enhancements |
Huawei, HiSilicon |
| R2-2403211 |
IOT NTN ASN1 RIL List |
Huawei, HiSilicon |
| R2-2403630 |
R18 IoT NTN stage 2 remaining issues |
Ericsson |
| R2-2403761 |
Report of [AT125bis][301][IoT NTN Enh] Preliminary RILs checking (Huawei) |
Huawei, HiSilicon |
| R2-2403763 |
[Draft] Reply LS on UE Location Information for NB-IoT NTN |
Qualcomm Incorporated |
| R2-2403770 |
Reply LS on UE Location Information for NB-IoT NTN |
RAN2 |
| R2-2403773 |
Stage-2 corrections on NR NTN |
THALES |
| R2-2403774 |
Introduction of IoT NTN enhancements |
Huawei, HiSilicon |
| R2-2403985 |
[Draft] Reply LS on UE Location Information for NB-IoT NTN |
Qualcomm Incorporated |
| 7.6.2 |
Stage 2 corrections |
|
| R2-2402213 |
Discussion on Autonomous GNSS Fix in C-DRX Inactive Time |
vivo |
| R2-2402373 |
Open issues with regards to GNSS operation |
PANASONIC R&D Center Germany |
| R2-2402772 |
Correction to Stage 2 on IoT NTN |
Huawei, HiSilicon |
| R2-2403480 |
Further discussion on stage-2 open issues for IoT NTN |
Nokia, Nokia Shanghai Bell |
| R2-2403764 |
[AT125bis][303][IoT NTN Enh] Open issues on GNSS enhancements (Nokia) |
Nokia, Nokia Shanghai Bell |
| 7.6.3 |
RRC Corrections |
|
| R2-2402185 |
Extending scenarios for t-service |
OPPO |
| R2-2402186 |
Discussion on GNSS operation for IoT NTN |
OPPO |
| R2-2402203 |
Correction to 36.331 for IoT NTN |
OPPO |
| R2-2402214 |
[V510] Correction on GNSS Measurement Failure |
vivo |
| R2-2402383 |
RRC c orrections on T390 and MO for IoT NTN |
ZTE Corporation, Sanechips |
| R2-2402584 |
[K001] Discussion on T317 expiry during GNSS measurement |
ASUSTeK |
| R2-2402705 |
Discussion on IOT NTN GNSS operation enhancement related open issues |
Xiaomi |
| R2-2402773 |
Remaining issues on GNSS operation enhancements |
Huawei, HiSilicon |
| R2-2402908 |
On the necessity of satellite assistance information for measurement in IoT NTN |
CATT |
| R2-2402913 |
[C651][C652][C653][C654] Corrections on Event D1, Event D2 and condEvent D2 |
CATT |
| R2-2403081 |
Remaining Issues on the GNSS Operation Enhancements |
Google Inc. |
| R2-2403335 |
Various RRC connection for IoT NTN including [S066][S067][S068] |
Samsung |
| R2-2403481 |
Remaining issue on gap length for autonomous GNSS measurement |
Nokia, Nokia Shanghai Bell |
| R2-2403491 |
[H004] Addition of polarization parameters |
Huawei, HiSilicon |
| R2-2403717 |
[X041][X042] Correction on GNSS operation enhancement |
Beijing Xiaomi Mobile Software |
| R2-2403723 |
[E801] Satellite assistance information for event D2 |
Ericsson |
| R2-2403765 |
Reply LS on improved GNSS operations in Rel-18 IoT NTN |
RAN2 |
| 7.6.4 |
MAC corrections |
|
| R2-2402204 |
Discussion on remaining issue on GNSS validity duration reporting |
OPPO |
| R2-2402215 |
Discussion on MAC Remaining Issues |
vivo |
| R2-2402384 |
MAC corrections to IoT NTN |
ZTE Corporation, Sanechips |
| R2-2402704 |
Discussion on issue related to UL Transmission Extension Update MAC Control Element |
Xiaomi |
| R2-2403220 |
Discussion on remaining MAC issues for Rel-18 IoT NTN |
MediaTek Inc. |
| R2-2403221 |
Corrections on UE behaviour on DRX for IoT NTN |
MediaTek |
| R2-2403482 |
On MAC open issues for IoT NTN |
Nokia, Nokia Shanghai Bell |
| R2-2403631 |
R18 IoT NTN GNSS extension |
Ericsson |
| 7.6.5 |
Corrections to other specs |
|
| R2-2402385 |
Corrections to idle mode measurement for IoT NTN |
ZTE Corporation, Sanechips |
| R2-2402812 |
Remaining issues on out-of-date GNSS fix |
Qualcomm Incorporated |
| R2-2402915 |
Corrections on Location-based Measurement Initiation in TS 36.304 |
CATT |
| R2-2403152 |
Miscellaneous correction for IoT-NTN |
Nokia |
| R2-2403336 |
On procedures and capabilities related to GNSS fix during C-DRX |
Samsung |
| R2-2403614 |
Corrections on uplink transmission extension |
Samsung |
| R2-2403768 |
Miscellaneous correction for IoT-NTN |
Nokia |
| 7.7.1 |
Organizational |
|
| R2-2402114 |
Reply LS on Satellite Switch with Resync (R1-2401748; contact: Apple) |
RAN1 |
| R2-2402129 |
Reply LS on RAN2 agreements for satellite switch with resync (R4-2403493; contact: Apple) |
RAN4 |
| R2-2402542 |
Discussion on reply LS from RAN1 and RAN4 for unchanged PCI |
CMCC |
| R2-2403632 |
Rapporteur input R18 NR NTN RRC |
Ericsson |
| R2-2403633 |
Rapporteur’s input R18 NR NTN RRC RILs |
Ericsson |
| R2-2403762 |
[AT125bis][302][NR NTN Enh] Preliminary RILs checking (Ericsson) |
Ericsson |
| R2-2403772 |
Miscellaneous corrections to Rel-18 NR NTN |
Ericsson |
| R2-2403776 |
IoT NTN corrections to stage 2 |
Ericsson, Huawei |
| R2-2404007 |
Corrections on UE behaviour on DRX for IoT NTN |
MediaTek |
| R2-2404034 |
Discussion on IoT NTN MAC CR |
MediaTek |
| 7.7.2 |
Stage 2 corrections |
|
| R2-2402798 |
Stage-2 corrections |
Samsung |
| 7.7.3 |
RRC corrections |
|
| R2-2402188 |
Discussion on soft switch unchanged PCI |
OPPO |
| R2-2402189 |
Discussion on ssb-TimeOffset |
OPPO |
| R2-2402190 |
[O600] Discussion on TN cell broadcasting NTN info |
OPPO |
| R2-2402216 |
[V500][V501] Correction on NTN-Config in case of Satellite Switch |
vivo |
| R2-2402217 |
Remaining Issue on Measurement during Hard Satellite Switch |
vivo |
| R2-2402218 |
Further Discussion on ssb-TimeOffset |
vivo |
| R2-2402263 |
SMTC configuration on satellite switch with re-sync |
NTU |
| R2-2402264 |
SMTC configuration on satellite switch with re-sync |
NTU |
| R2-2402335 |
SMTC configuration of target satellite for satellite switch with re-sync |
NTU |
| R2-2402543 |
[H063] Discussion on RACH-based solution for unchanged PCI |
CMCC |
| R2-2402585 |
[K005] Discussion on epoch time for satellite switch |
ASUSTeK |
| R2-2402586 |
Discussion on RACH-based satellite switch |
ASUSTeK |
| R2-2402799 |
Discussion on LS replies for Satellite Switch with Resync |
Samsung |
| R2-2402800 |
RIL S486, V500, V501, H063 |
Samsung |
| R2-2402831 |
Discussion on the remaining issues for NR NTN |
Xiaomi |
| R2-2402844 |
Discussion on Remaining Open Issues for Unchanged PCI Mechanism |
CATT |
| R2-2402850 |
[C650] [C651] Corrections on EventD2 and condEventD2 |
CATT |
| R2-2402867 |
Open issues on NR NTN measurement enhancement |
Apple |
| R2-2402882 |
Correction on referenceLocation2 |
Apple |
| R2-2403068 |
Remaining issues on unchanged PCI |
ZTE Corporation, Sanechips |
| R2-2403082 |
Provision of the TN PLMN ID in an NTN Cell |
Google Inc., Continental Automotive |
| R2-2403192 |
[H063] RACH-based satellite switching with re-sync |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R2-2403193 |
Discussion on satellite switch with re-sync |
Huawei, HiSilicon |
| R2-2403301 |
On RACH-based Satellite Switching with Resynchronization and Confirming Successful Switching |
Nokia, Nokia Shanghai Bell |
| R2-2403302 |
RRC Corrections and Proposed RIL [N131] and [N132] Resolutions for Rel-18 NTN |
Nokia |
| R2-2403490 |
RRC corrections on RILs [H115][H116] |
Huawei, HiSilicon |
| R2-2403634 |
Remaining issue on VSAT UEs |
Ericsson |
| R2-2403635 |
Remaining issues for soft switch with unchanged PCI |
Ericsson |
| R2-2403636 |
UE behaviour upon absence of EpochTime in TN cells |
Ericsson |
| R2-2403766 |
[AT125bis][305][NR NTN Enh] PDCCH order during satellite switch (Samsung |
Samsung |
| R2-2403767 |
Report of [AT125bis][306][NR NTN Enh] Corrections on (cond)EventD2 (Ericsson) |
Ericsson |
| R2-2403769 |
[Draft] LS on reference point for SSB-TimeOffset |
Apple |
| R2-2403771 |
LS on reference point for SSB-TimeOffset |
RAN2 |
| R2-2403951 |
Discussion on soft switch unchanged PCI |
OPPO |
| R2-2403952 |
[O600] Discussion on TN cell broadcasting NTN info |
OPPO |
| 7.7.4 |
MAC corrections |
|
| R2-2402774 |
Discussion on HARQ buffer flush during satellite switch with re-synchronization |
Huawei, HiSilicon |
| R2-2403637 |
TAT handling in RACH-less CHO |
Ericsson |
| 7.7.5 |
Corrections to other specs |
|
| R2-2402852 |
Correction on Location-based Measurement Initiation for Earth Fixed Cell in TS 38.304 |
CATT |
| R2-2402866 |
Clarification on UE operation during soft satellite switch with resync |
Apple |
| R2-2403069 |
Discussion on NTN FR2 UE capability |
ZTE Corporation, Sanechips |
| R2-2403070 |
CR to 38306 on NTN FR2 UE capability |
ZTE Corporation, Sanechips |
| R2-2403300 |
On Scheduling Restrictions in Satellite Soft Switching with Resynchronization – RAN1 and RAN4 feedback |
Nokia |
| 7.8.1 |
Organizational |
|
| R2-2402137 |
LS Reply on Aerial Pmax values (R4-2403830; contact: Nokia) |
RAN4 |
| R2-2402495 |
Capabilities for Rel-18 Enhanced LTE Support for UAV WI |
Huawei, HiSilicon |
| R2-2402497 |
Capabilities for Rel-18 NR Support for UAV WI |
Huawei, HiSilicon |
| R2-2402954 |
Correction to UE capability multiNS-PmaxAerial-r18 |
Qualcomm Incorporated, Nokia |
| R2-2403067 |
Correction on resource pool selection for A2X communication |
Samsung, Sharp |
| R2-2403303 |
On Aerial Pmax Values in the context of RAN4 LS [N135] |
Nokia |
| R2-2403304 |
Response LS on Aerial Pmax values |
Nokia |
| R2-2403957 |
Correction on resource pool selection for A2X communication |
Samsung, Sharp |
| R2-2404033 |
Corrections to Enhanced LTE Support for UAV (Uncrewed Aerial Vehicles) |
Qualcomm Incorporated, Nokia |
| 7.8.2 |
RRC RIL |
|
| R2-2402503 |
Report of [POST125][008][UAV] Draft TP for simulMultiTriggerSingleMeasReport |
Qualcomm Incorporated |
| R2-2402791 |
Corrections for NR Support for UAV (Uncrewed Aerial Vehicles) |
Qualcomm Incorporated |
| R2-2403365 |
E144, Standalone Aerial UE Capability |
Ericsson |
| R2-2403366 |
LS from RAN4, J061 |
Ericsson |
| R2-2403442 |
Further Consideration on SimuMultiTriggerSingleMeasReport |
ZTE Corporation, Sanechips |
| R2-2403725 |
NR UAV: Proposed resolutions to remaining ASN.1 RILs |
Qualcomm Incorporated |
| R2-2403953 |
Further Consideration on SimuMultiTriggerSingleMeasReport |
ZTE Corporation, Sanechips |
| R2-2403956 |
Corrections for NR Support for UAV (Uncrewed Aerial Vehicles) |
Qualcomm Incorporated |
| 7.8.3 |
Other |
|
| R2-2402312 |
Discussion on open issues of UAV UE capabilities |
CATT |
| R2-2402479 |
Discussion on flight path report |
Huawei, HiSilicon |
| 7.9.1 |
Organizational |
|
| R2-2403813 |
Rapp RRC CR for Rel-18 SL relay enhancement |
Huawei, HiSilicon |
| R2-2403815 |
Miscellaneous Rapporteur Corrections to 38.323 for SL Relay |
InterDigital, ZTE |
| R2-2403974 |
Introduction of NR sidelink relay enhancements |
LG Electronics (Rapporteur) |
| R2-2403975 |
Correction on 38.331 for SL Relay UE capability |
Samsung |
| R2-2403976 |
Correction on 38.306 for SL Relay UE capability |
Samsung |
| R2-2404030 |
RIL list for SL relay update |
Huawei |
| 7.9.2 |
Stage 2 corrections |
|
| R2-2402209 |
Discussion on stage-2 corrections |
OPPO |
| R2-2402428 |
Correction to 38.300 on Relay enhancement |
Xiaomi |
| R2-2402721 |
LTM in L2 relay case |
Lenovo |
| R2-2403311 |
Stage-2 Corrections for SL relay enhancements |
Huawei, HiSilicon |
| 7.9.3 |
RRC corrections |
|
| R2-2402208 |
[O400-407, O421], [O425], [O418, O427, O428], [O419], [Q581] Discussion on ToDo RILs for R18 Relay |
OPPO |
| R2-2402286 |
[B107] Discussion on IndirectPathFailureInformation message |
Lenovo, Apple, China Telecom, Sharp, InterDigital, Kyocera |
| R2-2402427 |
[X028] Correction on SIB1 forwarding in multipath |
Xiaomi |
| R2-2402504 |
[C262]Clarification on Indirect Path Failure for MP Scenario 1 |
CATT |
| R2-2402505 |
[C261]Handling of Indirect Path When Remote UE Enters RRC_IDLE |
CATT |
| R2-2402506 |
[C263]Clarification on U2U Remote UE Threshold Conditions |
CATT |
| R2-2402600 |
[X029,030,031] Correction on the relay reselection |
Xiaomi |
| R2-2402680 |
Rapp RRC CR for Rel-18 SL relay enhancement |
Huawei, HiSilicon |
| R2-2402681 |
RRC open issue list for Rel-18 SL relay |
Huawei, HiSilicon |
| R2-2402682 |
Report of [Post125][417][Relay] Rel-18 relay RRC open issues |
Huawei, HiSilicon |
| R2-2402717 |
[B108] on unsolicited SIB1 forwarding in MP |
Lenovo |
| R2-2402718 |
[B109] on sidelink RRC reconfiguration failure for U2U |
Lenovo |
| R2-2402719 |
[B112] on maintained indirect path during direct path addition v1.0 |
Lenovo |
| R2-2402720 |
[B113] TP on T390 in MP scenario |
Lenovo |
| R2-2402785 |
[H659] Network support for non-3GPP multi-path relay |
MediaTek Inc., OPPO, ZTE |
| R2-2402890 |
Discussion on remaining ASN.1 issues for Layer-2 UE-to-UE Relay |
Apple |
| R2-2402927 |
Discussion for the remaining issues for U2U relay |
LG Electronics Inc. |
| R2-2403140 |
Remaining issues and corrections on RRC specification |
Qualcomm Incorporated |
| R2-2403200 |
RSRP thresholds for U2N relay selection and re-selection |
Nokia |
| R2-2403314 |
[H064][H686] Discussion for RIL issues on U2U relay |
Huawei, HiSilicon |
| R2-2403357 |
Discovery [O419] Open Issues [Post125][417] and [X033] [X251] PC5 trigger for U2U Relay UE selection |
Beijing Xiaomi Mobile Software |
| R2-2403369 |
Remaining Open Issues in 38.331 |
Ericsson |
| R2-2403476 |
[Z756]SRAP configuration for non-RRC connected L2 U2U UEs |
ZTE, Sanechips |
| R2-2403477 |
Discussion on relay UE traffic pattern reporting in UAI |
ZTE, Sanechips |
| R2-2403552 |
discussion on flow-to-bearer mapping indication |
Sharp |
| R2-2403603 |
[N121][N122] RILs on sidelink relay |
Nokia |
| R2-2403607 |
E105, E267, E269 Issues on SL Relays |
Ericsson |
| R2-2403705 |
RIL list for Rel-18 SL relay enhancement |
Huawei, HiSilicon |
| R2-2403719 |
[X260] [X262] U2U Relay UE selection |
Beijing Xiaomi Mobile Software |
| R2-2403802 |
[AT125][402][Relay] Remaining prioritized issues on relay RRC (Huawei) |
Huawei, HiSilicon |
| 7.9.4 |
SRAP corrections |
|
| R2-2402206 |
Corrections for NR sidelink relay enhancements |
OPPO |
| R2-2402587 |
Clarification on UE ID pair allocation and determination |
ASUSTeK |
| R2-2403478 |
Discussion on SRAP corrections for U2U relay |
ZTE, Sanechips |
| R2-2403814 |
Corrections for NR sidelink relay enhancements |
OPPO, ZTE |
| 7.9.6 |
RLC and PDCP corrections |
|
| R2-2402207 |
Discussion on duplicated PDU submitted to indirect path RLC |
OPPO |
| R2-2402816 |
Miscellaneous Rapporteur Corrections to 38.323 for SL Relay |
InterDigital France R&D, SAS |
| R2-2403313 |
PDCP corrections on data volume calculation for multi-path relay |
Huawei, HiSilicon |
| R2-2403412 |
Clarification on PDCP with multi-path |
Nokia |
| R2-2403479 |
Discussion on PDCP corrections for MP |
ZTE, Sanechips |
| 7.9.7 |
UE capabilities |
|
| R2-2403139 |
UE capabilities on MP relay |
Qualcomm Incorporated |
| R2-2403312 |
UE capability corrections for multi-path operation |
Huawei, HiSilicon |
| R2-2403370 |
Remaining Open Issues in 38.306 |
Ericsson |
| R2-2403803 |
UE capability for simultaneous transmission on split bearer (Qualcomm) |
Qualcomm Incorporated |
| 7.9.8 |
Idle mode corrections |
|
| R2-2403602 |
Correction on 38.304 for SL Relays |
Ericsson |
| 7.10 |
IDC enhancements for NR and MR-DC |
|
| R2-2403431 |
Correction on the IDC Reporting |
ZTE Corporation, Sanechips |
| R2-2403444 |
IDC RIL list |
Xiaomi |
| R2-2403992 |
Summary of [AT125bis][003][IDC] Miscellaneous corrections for IDC (Xiaomi) |
Xiaomi (moderator) |
| 7.11.1 |
Organizational |
|
| R2-2402766 |
RIL list for MBS |
Huawei, HiSilicon |
| R2-2402767 |
MBS Rapporteur CR for RRC |
Huawei, HiSilicon, CATT, Samsung, LG Electronics Inc., CMCC, Xiaomi |
| R2-2403821 |
Summary of [AT125bis][601][eMBS] Updated RIL resolutions (Huawei) |
Huawei, HiSilicon |
| R2-2404019 |
MBS Rapporteur CR for RRC |
Huawei, HiSilicon, CATT, Samsung, LG Electronics Inc., CMCC, Xiaomi |
| R2-2404035 |
RIL list for MBS |
Huawei |
| 7.11.2 |
RRC corrections |
|
| R2-2402246 |
[V523][V531] Remaining Issues on Multicast Reception in INACTIVE |
vivo |
| R2-2402282 |
[C148][C149][C150] RRC Corrections for eMBS |
CATT, CBN, China Broadnet |
| R2-2402634 |
[Z695, Z696] Misc issues for multicast reception in RRC_INACTIVE with draft CR |
ZTE, Sanechips |
| R2-2402768 |
[H099] PTM configuration indication in the neighbour cell list for multicast |
Huawei, HiSilicon |
| R2-2402849 |
Discussion on frequency information reported for shared processing |
Xiaomi, Huawei, HiSilicon |
| R2-2403508 |
[S731][S732][S733] Issues for Multicast Reception |
Samsung |
| R2-2403547 |
MBS RILs |
Ericsson |
| R2-2403597 |
[N101] [N102] [N103] [N104] [N105] [N106] [N107] [N108][N109] Control plane aspects of multicast reception in RRC_INACTIVE state |
Nokia |
| R2-2403604 |
RIL_J009/J010/J011 MBS CP |
Sharp |
| 7.11.3 |
Other corrections |
|
| R2-2402868 |
Clarification on MAC reset for multicast reception in RRC_INACTIVE |
Apple, Samsung, CATT, Nokia, Huawei, HiSilicon, LG Electronics Inc. |
| R2-2403203 |
Error data handling for MBS |
Langbo |
| R2-2403546 |
Clarification for (e)RedCap UE supporting MBS in RRC_INACTIVE |
Ericsson |
| 7.12.1 |
Organizational and Stage-2 |
|
| R2-2402644 |
Requirement on the SIB1 indicator presence for the mobile IAB-node |
Huawei, HiSilicon |
| R2-2403169 |
RILs conclusions for MobileIAB |
Ericsson |
| R2-2403576 |
Clarification on supporting two logical DUs and connecting via stationary IAB node |
ZTE, Sanechips |
| R2-2403959 |
Clarification on supporting two logical DUs and connecting via stationary IAB node |
ZTE, Qualcomm, Ericsson, Samsung, Nokia |
| 7.12.2 |
Stage-3 |
|
| R2-2403168 |
Miscellaneous corrections on Mobile IAB |
Ericsson |
| R2-2404018 |
Miscellaneous corrections on Mobile IAB |
Ericsson |
| 7.12.2.2 |
Control plane corrections |
|
| R2-2402645 |
[H112, H113] Discussion on targetNTA and tci-StateID for mobile IAB |
Huawei, HiSilicon |
| R2-2402936 |
Mismatch of terminology between 38.304 and 38.331 |
Samsung |
| R2-2403170 |
Discussion on RILs conclusion MobileIAB |
Ericsson |
| R2-2403340 |
[S266][S267] Correction on setting mobile IAB support for PLMNs and NPNs |
Samsung |
| R2-2403447 |
Clarification to mobile IAB-MT measurement configuration |
Nokia |
| R2-2403448 |
Discussion on gNB-ID signalling |
Nokia |
| R2-2403575 |
Correction on frequency prioritization for mobile IAB |
ZTE, Sanechips |
| 7.13.1 |
Organizational |
|
| R2-2403156 |
WI RIL list for 36.331 for R18 SONMDT |
Huawei, HiSilicon |
| R2-2403157 |
Corrections to TS 36.331 for R18 SONMDT |
Huawei, HiSilicon |
| R2-2403241 |
BL CR on 38331 for SONMDT features |
Ericsson |
| R2-2403265 |
RIL issue list for SON |
Ericsson |
| R2-2403859 |
Corrections to TS 36.331 for R18 SONMDT |
Huawei, HiSilicon |
| R2-2403860 |
Corrections to 38331 for Rel-18 SONMDT |
Ericsson |
| 7.13.2 |
Papers related to RILs |
|
| R2-2402563 |
[V314] logged MDT configuration for SNPN |
vivo |
| R2-2402574 |
[F001][F018][F019][F020][F021][F022][F023] Correction on SPR |
Fujitsu, Lenovo, CATT |
| R2-2402575 |
[C306]Correction on fast MCG recovery enhancement |
Fujitsu |
| R2-2402653 |
[C303][C304][C307][C308][C311][C312][C315] [C351]Corrections about SONMDT issues |
CATT |
| R2-2403158 |
Discussion on open RILs and stage-2 issues for R18 SONMDT |
Huawei, HiSilicon |
| R2-2403197 |
RIL N022 and N123 related corrections |
Nokia |
| R2-2403242 |
Addressing SONMDT RILs |
Ericsson |
| R2-2403577 |
[J040][J041][J042][J043][J044]RILs for SON |
SHARP Corporation |
| R2-2403651 |
[S525][S526][S527][S528][S529][S530] RILs on SON/MDT |
Samsung |
| R2-2403856 |
LS to RAN3 on MDT for NPN |
RAN2 |
| 7.13.3 |
Other |
|
| R2-2402576 |
Correction on the reporting of TAC in Random access report |
Fujitsu, Ericsson, Lenovo, Huawei, HiSilicon, CATT, Xiaomi, Samsung, SHARP |
| R2-2403074 |
Consideration on SON/MDT remaining issues |
ZTE Corporation, Sanechips |
| R2-2403196 |
Considerations on including TAC in RA reports |
Nokia |
| R2-2403425 |
Configuring T310 and T312 thresholds at the time of PSCellChange |
Samsung |
| R2-2403663 |
Miscellaneous correction to TS 38.300 |
Ericsson |
| 7.14.1 |
Organizational |
|
| R2-2402103 |
LS on area scope handling for QoE measurement collection (C1-241717; contact: Ericsson) |
CT1 |
| R2-2403246 |
Correction of Enhancement on NR QoE management and optimizations for diverse services |
Ericsson |
| R2-2403247 |
RIL issue list for QoE |
Ericsson |
| R2-2404010 |
Correction of Enhancement on NR QoE management and optimizations for diverse services |
Ericsson |
| R2-2404011 |
RIL issue list for QoE |
Ericsson |
| 7.14.2 |
QoE measurements in RRC_IDLE INACTIVE |
|
| R2-2403159 |
Discussion on serving cell for MBS QoE collection H079H082 |
Huawei, HiSilicon |
| R2-2403249 |
RIL issues related to QoE measurements |
Ericsson |
| 7.14.3 |
Other corrections |
|
| R2-2403075 |
Consideration on QoE remaining issues |
ZTE Corporation, Sanechips |
| R2-2403248 |
Open issues for QoE measurements |
Ericsson |
| R2-2403486 |
Correction for NR QoE configurations release in inter-RAT HO |
Nokia, Nokia Shanghai Bell |
| 7.15.1 |
Organizational |
|
| R2-2402111 |
Reply to LS on Sidelink CSI Reporting MAC-CE for SL-CA (R1-2401727; contact: LGE) |
RAN1 |
| R2-2402115 |
LS on new higher layer parameter for intra-cell guard band (R1-2401756; contact: OPPO) |
RAN1 |
| R2-2402225 |
RRC Open Issue list for R18 SL-Evo |
OPPO |
| R2-2402481 |
MAC Open Issue list for R18 SL-Evo |
LG Electronics Inc. |
| R2-2402572 |
Discussion on UE behaviour when no TX profile provided for SL CA |
vivo |
| R2-2403586 |
Discussion on No Tx profile |
ZTE Corporation, Sanechips |
| 7.15.2 |
Control plane corrections |
|
| R2-2402226 |
Correction on Release-18 SL Evolution |
OPPO |
| R2-2402227 |
Left issues on RRC |
OPPO |
| R2-2402228 |
[O321][O322] Discussion on SL features co-configuration |
OPPO |
| R2-2402362 |
RRC corrections for SL evolution |
Huawei, HiSilicon |
| R2-2402571 |
Discussion on whether/how to configure both SL-U and SL-CA in SIB12 |
vivo |
| R2-2402601 |
Correction on TS 38.331 for SL |
Xiaomi |
| R2-2402642 |
[Z710][Z711] Correction on allowed carrier set for SRB |
ZTE Corporation, Sanechips |
| R2-2402797 |
Miscellaneous Rapporteur Stage 2 Corrections for NR Sidelink Evolution |
InterDigital France R&D, SAS |
| R2-2402914 |
RIL list for R18 SL |
OPPO |
| R2-2403036 |
SL evolution open issues |
Nokia |
| R2-2403079 |
Corrections to TS 38.331 for NR SL evolution |
CATT |
| R2-2403264 |
[H089] Clarification on description of sl-NumOfSSSBRepetition |
Huawei, HiSilicon |
| R2-2403383 |
Discussion on postponed RIL [C613] |
CATT, ZTE Corporation, Sanechips, Ericsson, Apple, Xiaomi, NEC, Qualcomm Incorporated, InterDigital Inc., LG Electronics |
| R2-2403716 |
[W101] RRC correction on SL consistent LBT failure |
NEC |
| R2-2403923 |
Summary of [AT125bis][102][V2X/SL] (CATT) |
CATT (Rapporteur) |
| R2-2403924 |
LS on Sidelink Feature Co-configuration |
RAN2 |
| R2-2403925 |
LS on interpretation when TX profile is not provided |
RAN2 |
| R2-2403926 |
Miscellaneous Rapporteur Stage 2 Corrections for NR Sidelink Evolution |
InterDigital |
| R2-2403928 |
[AT125bis][101][V2X/SL] (OPPO) |
OPPO |
| R2-2403930 |
Correction on Release-18 SL Evolution |
OPPO |
| 7.15.3 |
User plane corrections |
|
| R2-2402205 |
Corrections on SL-U for MAC layers |
SHARP Corporation |
| R2-2402229 |
Left issues on MAC |
OPPO |
| R2-2402391 |
MAC corrections for SL evolution |
Huawei, HiSilicon |
| R2-2402482 |
Left issues on MAC |
LG Electronics Inc. |
| R2-2402602 |
Correction on TS 38.321 for SL |
Xiaomi |
| R2-2402605 |
Discussion on remaining issue of TS 38.321 |
NEC |
| R2-2402606 |
Discussion on the missing agreement in TS 38.321 |
NEC, InterDigital |
| R2-2402643 |
Discussion on remaining issues on user plane for SL evo |
ZTE Corporation, Sanechips |
| R2-2402889 |
Correction on TX carrier (re-)selection |
Apple |
| R2-2402916 |
MAC correction on Release-18 SL Evolution |
LG Electronics Inc. |
| R2-2402946 |
Correction to resource selection for LTE-NR cochannel scenario |
Ericsson, LG Electronics Inc. |
| R2-2402947 |
discussion on reply LS from RAN1 on SL CSI reporting MAC CE for SL CA |
Ericsson |
| R2-2403047 |
Discussion on the postponed issue for Re-evaluation/Pre-emption in MCSt |
CATT |
| R2-2403413 |
Clean up on SL LBT |
Nokia |
| R2-2403927 |
Discussion on CSI report for SL-CA |
Qualcomm |
| R2-2403931 |
Correction on Release-18 Sidelink evolution |
LG |
| 7.17.1 |
Organizational |
|
| R2-2402483 |
RILs_conclusion_MUSIM |
vivo(Rapporteur) |
| R2-2402484 |
Correction on NR MUSIM enhancements |
vivo |
| R2-2403999 |
RILs_conclusion_MUSIM |
vivo(Rapporteur) |
| R2-2404000 |
Correction on NR MUSIM enhancements |
vivo |
| 7.17.2 |
RRC |
|
| R2-2402313 |
[S854] Discussion on MUSIM remaining issues |
CATT |
| R2-2402451 |
Further discussion on open Issue#8 about reconfiguration failure for MUSIM |
Huawei, HiSilicon, vivo, DENSO CORPORATION, China Telecom, Qualcomm Incorporated, Samsung |
| R2-2402485 |
Discussion on the capability restriction during RRC re-establishment |
vivo |
| R2-2402968 |
[H104][H105][H106][H108][H109] Discussion on MUSIM RILs |
Huawei, HiSilicon |
| R2-2403142 |
Discussion on security issue for early indication |
Huawei, HiSilicon |
| R2-2403146 |
Remaining open issues for Dual TX/TX MUSIM Operation |
Nokia |
| R2-2403147 |
Additional capability restrictions related to measurement gaps |
Nokia |
| R2-2403150 |
Corrections on need for gap for MUSIM purpose |
OPPO |
| R2-2403151 |
Corrections on the feature for keeping MUSIM gaps when collision |
OPPO |
| R2-2403262 |
Dependency of Musim-NeedForGaps with Nr-NeedForGap-Reporting capability |
Samsung |
| R2-2403324 |
Open issues on MUSIM Band restrictions |
Ericsson |
| R2-2403325 |
Discussion on bandEntryIndex at handover |
Ericsson |
| R2-2403428 |
Consideration on the UAI Processing during Handover |
ZTE Corporation, Sanechips |
| R2-2403429 |
Consideration on the Fallback Relationship for the Affected Band Combinations |
ZTE Corporation, Sanechips |
| R2-2403430 |
[RIL-Z116] Consideration on the MUSIM UAI Setting |
ZTE Corporation, Sanechips |
| R2-2403522 |
[L012] Wait timer issue when performing Handover |
LG Electronics Inc. |
| R2-2403560 |
No capability restriction in first UAI after early indication |
Samsung, Huawei, HiSilicon, ZTE Corporation, Sanechips |
| R2-2403562 |
[S860] Discussion on early indication of MUSIM temporary capability restriction in RRCReestablishmentComplete |
Samsung, Intel Corporation, CATT, Xiaomi, Qualcomm, Apple, China Telecom, NEC, vivo, Huawei, HiSilicon |
| R2-2403617 |
[S854][S862][S863] RILs on MUSIM |
Samsung |
| R2-2403715 |
[Z102][S863] Consideration on the musim-MaxCC Reporting |
ZTE Corporation, Sanechips |
| R2-2403728 |
[H104][H105][H106][H108][H109] Discussion on MUSIM RILs |
Huawei, HiSilicon |
| R2-2403739 |
[Z116][Z102][S863] Consideration on the MUSIM UAI Reporting |
ZTE Corporation, Sanechips |
| R2-2403741 |
[AT125bis][201][MUSIM] Offline discussion on the remaining RILs and other issues (vivo) |
Rapporteur (vivo) |
| 7.18.1 |
Organizational |
|
| R2-2402756 |
[E075] Report of [POST125][026][MT-SDT]: Harmonising the handling of SDT ongoing and T319a |
ZTE Corporation(rapporteur) |
| R2-2402757 |
[E075] SDT corrections for harmonizing T319a and SDT ongoing labels |
ZTE Corporation (rapporteur) |
| R2-2402758 |
[E075] SDT corrections for harmonizing T319a and SDT ongoing labels |
ZTE Corporation (rapporteur) |
| R2-2403714 |
SDT RIL List |
ZTE Corporation (rapporteur) |
| R2-2403724 |
SDT CR for agreed RILs |
ZTE Corporation (rapporteur) |
| 7.18.2 |
Others |
|
| R2-2402298 |
discussion on RACH based SDT |
PML |
| R2-2402700 |
Discussion on SDT procedure ongoing |
Ericsson |
| R2-2403083 |
Correction on sdt-LogicalChannelSR-DelayTimer applicability |
Nokia, Nokia Shanghai Bell |
| 7.19.1 |
Organizational |
|
| R2-2402104 |
LS on Rel-18 RedCap enhancements work (C1-241809; contact: Huawei) |
CT1 |
| R2-2402450 |
Miscellaneous corrections on TS 38.304 for eRedCap |
Huawei, HiSilicon |
| R2-2402619 |
Miscellaneous corrections on TS 38.321 for eRedCap |
vivo (Rapporteur) |
| R2-2403394 |
Miscellaneous corrections for eRedCap |
Ericsson |
| R2-2403397 |
RIL List for eRedCap - after RAN2#125 |
Ericsson |
| R2-2403861 |
Miscellaneous corrections for eRedCap |
Ericsson |
| 7.19.2 |
Papers related to RILs |
|
| R2-2402449 |
Clarification on remaining RIL issues for eRedcap and proposed TP to RRC |
Xiaomi Communications |
| R2-2403401 |
Discussion on RILs E158 E159 and V179 on eRedCap UEs |
Ericsson |
| R2-2403687 |
[V179] Discussion on more details for V179 |
vivo, Guangdong Genius |
| R2-2403688 |
[X110] Discussion on MsgA PUSCH less than 5MHz |
vivo, Guangdong Genius |
| 7.19.3 |
Other |
|
| R2-2402382 |
MAC corrections for supporting 2-step RACH for eRedCap |
ZTE Corporation, Sanechips |
| R2-2402448 |
Remaining issues on the use of 2-step RA resources for eRedCap UEs |
Xiaomi Communications |
| R2-2402620 |
Discussion on remaining issues for eRedCap |
vivo, Guangdong Genius |
| R2-2403053 |
Need for clarification on 1 Rx and 2 Rx (e)RedCap UE barring |
Telit Communications S.p.A. |
| R2-2403271 |
1 Rx and 2 Rx eRedCap UE barring |
Nokia |
| R2-2403399 |
Discussion on 1 Rx and 2 Rx eRedCap UE barring |
Ericsson |
| R2-2403667 |
Remaining issues on eRedCap |
LG Electronics Inc. |
| 7.20.1 |
Organizational |
|
| R2-2402801 |
MAC open issue list for MIMO evolution |
Samsung, NTT DOCOMO, INC. |
| R2-2403729 |
NR RIL List Q2 Phase 1 MIMO (v102) |
Ericsson |
| R2-2404004 |
Corrections on Rel-18 MIMOevo for TS 38.321 |
Samsung |
| R2-2404017 |
Correction to MIMO Evolution |
Ericsson |
| R2-2404022 |
Corrections on Rel-18 MIMOevo for TS 38.321 |
Samsung |
| R2-2404027 |
NR RIL List Q2 MIMO Post125bis |
Ericsson |
| 7.20.2 |
MAC |
|
| R2-2402537 |
Discussion on CG-SDT Related TAT Handling with Two TAs |
CATT |
| R2-2402802 |
MAC Remaining issues on MIMO |
Samsung |
| R2-2402820 |
Discussion on co-existence of SDT and the configuration of 2 PTAGs |
OPPO |
| R2-2402842 |
Remaining issue on STx2P PHR |
LG Electronics Inc. |
| R2-2402843 |
Remaining issues on SDT and 2-PTAGs |
LG Electronics Inc. |
| R2-2402940 |
Discussion on remaining issues of NR MIMO evo |
Qualcomm Incorporated |
| R2-2403084 |
Correction on multi-TRP STx2P PHR MAC CE |
Nokia |
| R2-2403292 |
Correction on RA for 2TA |
Huawei, HiSilicon |
| R2-2403375 |
Cosideration On PHR and PHR MA CE for STxMP |
ZTE Corporation, Sanechips |
| R2-2403376 |
Discussion On Remaining Issues on mTRP with 2TA |
ZTE, Samsung, CATT, OPPO |
| 7.20.3 |
RRC |
|
| R2-2402288 |
Discussion on CBRS configuration for CJT |
NEC |
| R2-2402538 |
[C506][C508][C512][C513][C514][C515][C516][C519] RRC Corrections for MIMO |
CATT, Ericsson |
| R2-2402803 |
RIL S952, S953, S954, S955, S956, S957, C515, C516, E228, E229 |
Samsung |
| R2-2402804 |
RIL S958, S959 on codebook CBSR |
Samsung, Xiaomi, Ericsson |
| R2-2403134 |
[N110] Correction on Unified TCI operation |
Nokia |
| R2-2403222 |
Remaining aspects on RRC for MIMOevo, E228, E229, C515, C516 |
Ericsson |
| R2-2403293 |
[H152][H153] RRC corrections for MIMO |
Huawei, HiSilicon |
| R2-2403742 |
Summary of offline discussion [202] |
Ericsson |
| R2-2403743 |
Draft MIMO CR capturing outcome of offline [202] |
Ericsson |
| R2-2403988 |
TP to remove unnecessary ToReleaseList |
Huawei, HiSilicon |
| 7.21.1 |
Organizational |
|
| R2-2402107 |
Reply LS on UE capabilities for MPR reduction (R1-2401627; contact: Nokia) |
RAN1 |
| R2-2402135 |
LS on power class capability for NR coverage enhancement (R4-2403659; contact: LGE) |
RAN4 |
| R2-2402753 |
Correction on CE capability |
ZTE Corporation |
| R2-2403694 |
Discussion on LS from R4 on power class capability for NR coverage |
CATT |
| R2-2403703 |
CE RIL resolutions |
Huawei, HiSilicon |
| R2-2403726 |
RRC CR for capability for NR coverage enhancement |
LG Electronics Inc. |
| R2-2403727 |
38.306 CR for capability for NR coverage enhancement |
LG Electronics Inc. |
| R2-2403911 |
RRC CR for capability for NR coverage enhancement |
LG Electronics Inc. |
| R2-2403912 |
38.306 CR for capability for NR coverage enhancement |
LG Electronics Inc. |
| 7.21.2 |
Control plane corrections |
|
| R2-2402242 |
[M871][M872] On the number of RACH partitions |
MediaTek Inc. |
| R2-2402359 |
Clarification on rsrp-ThresholdMsg1-RepetitionNumX |
Huawei, HiSilicon |
| 7.21.3 |
User plane corrections |
|
| R2-2402224 |
Support of RO Mask with Preamble Repetition |
vivo |
| R2-2402360 |
Discussion on mask index for CFRA and other UP issues |
Huawei, HiSilicon |
| R2-2402367 |
Correction to PHR MAC CE Design for assumed PUSCH reporting |
Samsung Electronics Co., Ltd, Nokia, Nokia Shanghai Bell, Lenovo |
| R2-2402368 |
CFRA with Msg1 Repetition - RO Mask handling |
Samsung Electronics Co., Ltd, China Telecom |
| R2-2402533 |
Discussion on ra-ssb-OccasionMaskIndex for CFRA with Msg1 repetition |
China Telecom |
| R2-2402534 |
Draft LS on ra-ssb-OccasionMaskIndex handling for CFRA with Msg1 repetition |
China Telecom |
| R2-2402701 |
Discussion on Msg1 Repetitions and use of ra-ssb-OccasionMaskIndex |
Ericsson |
| R2-2402711 |
Updating RO Mask index for multiple PRACH repetitions |
Ericsson |
| R2-2402752 |
RO Mask Index in CFRA with Msg1 Repetition |
ZTE Corporation |
| R2-2402909 |
Correction for assumed PUSCH PHR |
InterDigital |
| R2-2403085 |
PRACH Mask for Msg1 repetition |
Nokia |
| R2-2403086 |
Draft LS on PRACH mask applicability for Msg1 repetition |
Nokia |
| R2-2403120 |
Discussions on PRACH Mask for CFRA with Msg1 repetition |
NEC Corporation. |
| R2-2403125 |
Discussion on reporting for MPE and assumed PUSCH |
NEC Corporation, ZTE Corporation, Sanechips |
| R2-2403256 |
RO Masking for Msg-1 repetition |
Qualcomm Incorporated |
| R2-2403668 |
PRACH Mask for CFRA with Msg1 repetition |
LG Electronics Inc. |
| R2-2403678 |
Discussion on RO mask index in CFRA with Msg1 repetition |
CATT |
| R2-2403914 |
[Draft] LS on PRACH mask index handling for MSG1 repetition |
China Telecom |
| R2-2403915 |
LS on PRACH mask index handling for MSG1 repetition |
RAN2 |
| 7.23.1 |
Organizational |
|
| R2-2402518 |
Corrections to URLLC and Timing Resiliency |
Ericsson |
| R2-2403722 |
Corrections to URLLC and Timing Resiliency |
Ericsson |
| 7.23.2 |
General |
|
| R2-2402295 |
[V530] Correction on VarTSS-Info |
vivo |
| R2-2403051 |
Simplification of SIB9 reception |
Nokia, Nokia Shanghai Bell, Ericsson |
| 7.24.1 |
TEI proposals by Other Groups |
|
| R2-2402105 |
Reply LS on Mitigation of Downgrade attacks (C1-241848; contact: Apple) |
CT1 |
| R2-2402122 |
Reply LS on Trace functionality extension in N3IWF for non-3GPP access scenarios (R3-241066; contact: Ericsson) |
RAN3 |
| R2-2402123 |
Reply LS on user consent for trace reporting (R3-241115; contact: Ericsson) |
RAN3 |
| R2-2402147 |
Reply LS on Multiple Trace/MDT configurations (S5-240798; contact: Ericsson) |
SA5 |
| R2-2403094 |
Restriction on RAT utilization |
Vodafone |
| R2-2403095 |
Restriction on RAT utilization |
Vodafone |
| R2-2403538 |
Introduction of LCS User Plane |
Ericsson, Intel Corporation, Huawei, HiSilicon, ZTE Corporation, vivo |
| 7.24.2.1 |
2Rx XR |
|
| R2-2403105 |
Emergency call support for 2Rx XR UE |
Huawei, HiSilicon |
| R2-2403106 |
Clarification for UE capability for 2Rx XR |
Huawei, HiSilicon |
| R2-2403107 |
Correction on cell status for 2Rx XR UE |
Huawei, HiSilicon |
| R2-2403382 |
38331_Correction for the selected band for 2RX XR UE capability checking |
Xiaomi Communications |
| 7.24.2.2 |
Other RAN2 TEI-18 |
|
| R2-2402112 |
LS on separate CFR introduced in Rel-18 TEI of MBS for RedCap UE applied for eRedCap UE (R1-2401732; contact: ZTE) |
RAN1 |
| R2-2402210 |
Remove of AS condition checking of SUI for U2N Relay communication |
OPPO, Apple |
| R2-2402211 |
Discussion on AS condition checking of SUI for U2N Relay communication |
OPPO, Apple |
| R2-2402283 |
Correction to 38.300 for redcap CFR of MBS |
CATT, CBN, China Broadnet |
| R2-2402324 |
Remaining Issue on Broadcast CFR for Redcap |
vivo |
| R2-2402329 |
Discussion on specification modification of redirection to GERAN |
vivo, Samsung |
| R2-2402330 |
36.331 Correction on redirection to GERAN |
vivo, Nokia, Nokia Shanghai Bell |
| R2-2402372 |
Corrections for MUSIM paging cause forwarding |
Samsung Electronics Co., Ltd |
| R2-2402418 |
Corrections for Bluetooth AoA/AoD [BT-AoA-AoD] |
Intel Corporation |
| R2-2402631 |
MCCH Search space for (e)RedCap UE MBS broadcast reception |
ZTE, Sanechips |
| R2-2402769 |
Clarification on MBS search spaces configuration for (e)Redcap [RedCapMBS_Bcast] |
Huawei, CATT, Xiaomi, HiSilicon |
| R2-2402770 |
Correction on MBS search spaces configuration for (e)Redcap [RedCapMBS_Bcast] |
Huawei, CATT, Xiaomi, HiSilicon |
| R2-2402900 |
Summary of [POST125][022][RedCap emergency calls] Discussion |
Apple |
| R2-2402901 |
Introduction of barring exemption for RedCap UEs for emergency calls [RedCap_EM_Call] |
Apple, China Telecom, Vodafone, Verizon, TMobile USA, ZTE, Vivo, Ericsson |
| R2-2402902 |
Introduction of barring exemption for RedCap UEs for emergency calls [RedCap_EM_Call] |
Apple, China Telecom, Vodafone, Verizon, TMobile USA, ZTE, Vivo, Ericsson |
| R2-2402903 |
Introduction of barring exemption for RedCap UEs for emergency calls [RedCap_EM_Call] |
Apple, China Telecom, Vodafone, Verizon, TMobile USA, ZTE, Vivo, Ericsson |
| R2-2402904 |
Introduction of barring exemption for eRedCap UEs for emergency calls |
Apple, China Telecom, Vodafone, Verizon, TMobile USA, ZTE, Vivo, Ericsson |
| R2-2403000 |
Emergency Call in Feature specific cells |
Lenovo |
| R2-2403087 |
SDT BFR timer being not configured [RA-SDT_BeamFailure] |
Nokia, Sony, Nokia Shanghai Bell |
| R2-2403088 |
Introduction of SDT BFR [RA-SDT_BeamFailure] |
Nokia, Sony, Nokia Shanghai Bell |
| R2-2403108 |
Correction for resumeIndication [SDT_ReleaseEnh] |
Huawei, HiSilicon, Nokia, ZTE Corporation, Sanechips |
| R2-2403141 |
Introduction of barring exemption for eRedCap UEs for emergency calls [RedCap_EM_Call] |
Apple, China Telecom, Vodafone, Verizon, TMobile USA, ZTE, Vivo, Ericsson |
| R2-2403183 |
Enhancing leaving and entering conditions in measurement report [meas_enter_leave] |
Ericsson, T-Mobile USA, Turkcell, Rakuten Mobile, BT Plc., NTT Docomo, Deutsche Telekom, MediaTek Inc., Verizon, AT&T, Vodafone, Continental Automotive, KDDI, Charter, NEC, Telecom Italia, CATT, Reliance Jio |
| R2-2403184 |
[E230] Clarification on CIO configured within ReportConfig [CIO_in_ReportConfig] |
Ericsson |
| R2-2403315 |
[Draft] LS on emergency call support for (e)RedCap in barred cells |
Apple [to be RAN2] |
| R2-2403358 |
LS to RTCM on GNSS positioning and integrity |
Swift Navigation, Ericsson |
| R2-2403472 |
Introduction of barring exemption for eRedCap UEs for emergency calls [RedCap_EM_Call] |
Apple, China Telecom, Vodafone, Verizon, TMobile USA, ZTE, Vivo, Ericsson |
| R2-2403539 |
LPP support for sub 1s location information reporting periodicity |
Ericsson, AT&T, T-Mobile, Vivo, Deutsche Telekom |
| R2-2403548 |
MBS RedCap CFR in Stage 2 |
Ericsson |
| R2-2403549 |
MBS and eRedCap UE |
Ericsson |
| R2-2403578 |
Failure information in RLF report for inter-RAT mobility |
SHARP Corporation |
| R2-2403598 |
MBS operation with eDRX MICO [TEI18 NR_MBS_enh] |
Nokia, Ericsson |
| R2-2403605 |
LPP support for sub 1s location information reporting periodicity |
Ericsson, AT&T, T-Mobile, Vivo, Deutsche Telekom |
| R2-2403792 |
[B021] Missing posSibType2-17a in list of posSIB types [PosL2RemoteUE] |
MediaTek Inc., Lenovo |
| R2-2403793 |
LPP support for sub 1s location information reporting periodicity |
Ericsson, AT&T, T-Mobile, Vivo, Deutsche Telekom, Huawei, HiSilicon, Vodafone |
| R2-2403794 |
Corrections for Bluetooth AoA/AoD [BT-AoA-AoD] |
Ericsson, Intel Corporation |
| R2-2403973 |
LPP support for sub 1s location information reporting periodicity |
Ericsson, AT&T, T-Mobile, Vivo, Deutsche Telekom, Huawei, HiSilicon, Vodafone |
| R2-2403982 |
LS on emergency call support for €RedCap in barred cells |
RAN2 |
| R2-2403989 |
Enhancing leaving and entering conditions in measurement report [meas_enter_leave] |
Ericsson, T-Mobile USA, Turkcell, Rakuten Mobile, BT Plc., NTT Docomo, Deutsche Telekom, MediaTek Inc., Verizon, AT&T, Vodafone, Continental Automotive, KDDI, Charter, NEC, Telecom Italia, CATT, Reliance Jio |
| R2-2403997 |
LS on emergency call support for €RedCap in barred cells |
RAN2 |
| 7.25.1.6 |
ATG |
|
| R2-2402128 |
LS on Layer-2/3 ATG UE features (R4-2403467; contact: CMCC) |
RAN4 |
| R2-2403013 |
ATG ASN1 RIL List |
CMCC |
| R2-2403014 |
Corrections to NR ATG |
CMCC |
| 7.25.1.7 |
Other |
|
| R2-2402113 |
LS on NCD-SSB time offset for non-RedCap UEs in TDD (R1-2401743; contact: Vodafone) |
RAN1 |
| R2-2402126 |
Reply LS on RRC network assistant signalling for advanced receiver on MU-MIMO scenario (R4-2403086; contact: China Telecom, CATT) |
RAN4 |
| R2-2402138 |
Reply to LS on inter-frequency neighbour cells supporting NR dedicated spectrum less than 5 MHz for FR1 (R4-2403852; contact: Huawei) |
RAN4 |
| R2-2402139 |
LS on applicable release of per FS TxD capability (R4-2403857; contact: OPPO) |
RAN4 |
| R2-2402327 |
Discussion on neighbour cells supporting dedicated spectrum less than 5MHz |
vivo |
| R2-2402496 |
Report of [POST125] [012] [less5MHz] Backward compatibility issue |
Qualcomm Incorporated |
| R2-2402535 |
Discussion on RRC signalling for advanced receiver on MU-MIMO scenario |
China Telecom, CATT |
| R2-2402536 |
Correction on RRC signalling for advanced receiver |
China Telecom, CATT |
| R2-2402621 |
Miscellaneous corrections on TS 38.300 for BWP operation without restriction |
vivo |
| R2-2402622 |
RIL list for BWP_Wor |
vivo |
| R2-2402623 |
[V994][V995] Miscellaneous corrections on TS 38.331 for BWP operation without restriction |
vivo |
| R2-2402787 |
Remaining aspects of NR less than 5 MHz not concluded by [POST125] [012] |
Qualcomm Incorporated |
| R2-2402788 |
Introduction of NR support for dedicated spectrum less than 5MHz for FR1 |
Qualcomm Incorporated |
| R2-2402789 |
Introduction of NR support for dedicated spectrum less than 5MHz for FR1 |
Qualcomm Incorporated |
| R2-2402790 |
[DRAFT] Reply LS on inter-frequency neighbour cells supporting NR dedicated spectrum less than 5 MHz for FR1 |
Qualcomm Incorporated |
| R2-2402924 |
[draft] LS on RRM enhancements for NR FR2 HST |
Samsung |
| R2-2403167 |
Remaining issues on advance receivers |
Ericsson |
| R2-2403353 |
Discussion on indicating less than 5 MHz neighbor carriers in SIBs |
Huawei, HiSilicon |
| R2-2403354 |
Introduction of less than 5MHz carriers for NR FR1 |
Huawei, HiSilicon |
| R2-2403355 |
Introduction of less than 5MHz carriers for NR FR1 |
Huawei, HiSilicon |
| R2-2403960 |
Reply LS on inter-frequency neighbour cells supporting NR dedicated spectrum less than 5 MHz for FR1 |
RAN2 |
| R2-2403961 |
Introduction of NR support for dedicated spectrum less than 5MHz for FR1 |
Qualcomm Incorporated |
| R2-2403962 |
Introduction of NR support for dedicated spectrum less than 5MHz for FR1 |
Qualcomm Incorporated |
| R2-2403963 |
LS on RRM enhancements for NR FR2 HST |
RAN2 |
| R2-2404038 |
Reply LS on inter-frequency neighbour cells supporting NR dedicated spectrum less than 5 MHz for FR1 |
RAN2 |
| 7.25.2 |
RAN1 led items |
|
| R2-2402110 |
LS on TS38.300 TP for Multi-cell scheduling in Rel-18 (R1-2401716; contact: NTT DOCOMO) |
RAN1 |
| R2-2402116 |
Reply LS on UL Tx switching (R1-2401776; contact: NTT DOCOMO) |
RAN1 |
| R2-2402134 |
Reply LS on UL Tx switching (R4-2403657; contact: vivo) |
RAN4 |
| R2-2403706 |
RIL list for Rel-18 MC enhancement |
Huawei, HiSilicon |
| 7.25.3 |
Other |
|
| R2-2403529 |
Introduction of NR UE Rx-Tx time difference measurement in NR UL E-CID [ECID-UERxTx] |
Ericsson, Polaris Wireless, China Telecom, NTT Docomo, AT&T, FirstNet, Intel, Comtech, Nokia, Nokia Shanghai Bell, Verizon Wireless, Huawei, ZTE |
| 8.0 |
General |
|
| R2-2402140 |
LS Reply to SA5 on LS on new definitions of energy efficiency and energy consumption (S2- 2403444; contact: OPPO) |
SA2 |
| R2-2402142 |
LS on per UE energy consumption in RAN (S2-2403733; contact: Vodafone) |
SA2 |
| R2-2402144 |
Clarification on the requirements for NTZ (S2-2403859; contact: LGE) |
SA2 |
| R2-2402148 |
Reply LS RP-240031 on clarification on requirements for NTZ (RP-240810; contact: InterDigital) |
RAN |
| R2-2402149 |
Reply LS RP-240029 on per UE energy consumption in RAN (RP-240825; contact: InterDigital) |
RAN |
| 8.1.1 |
Organizational |
|
| R2-2402146 |
LS on the progress update of AI/ML Management specifications in SA5 (S5-238107; contact: NEC, Intel) |
SA5 |
| R2-2403213 |
Discussion on SA5 AIML management aspects |
NEC |
| R2-2403628 |
RAN2 Work Plan for Rel-19 WI on AI/ML for NR air interface |
Ericsson |
| 8.1.2 |
Functionality based LCM |
|
| R2-2402247 |
other aspect of AI/ML LCM |
TCL |
| 8.1.2.1 |
LCM for NW-sided model |
|
| R2-2402172 |
LCM for NW-sided model |
OPPO |
| R2-2402268 |
Discussion on the LCM for NW-sided model |
Fujitsu |
| R2-2402299 |
Discussion on LCM for NW-sided model |
CATT |
| R2-2402419 |
Discussion on LCM for NW-sided model |
Intel Corporation |
| R2-2402429 |
Discussion on LCM for NW-sided model |
Xiaomi |
| R2-2402486 |
Discussion on functionality based LCM for NW-sided model |
vivo |
| R2-2402651 |
Considerations on LCM for NW side model |
ZTE Corporation |
| R2-2402670 |
LCM for Network sided model |
NEC |
| R2-2402729 |
Discussion on LCM for NW-sided model |
Lenovo |
| R2-2402783 |
Functionality-based LCM for NW sided model |
Samsung |
| R2-2402795 |
Lifecycle management for Network-sided model |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2402861 |
General LCM framework for NW-sided model |
Apple |
| R2-2402959 |
NW-side AI/ML Functionality based LCM |
Nokia |
| R2-2403019 |
Discussion on LCM for NW-sided model |
CMCC |
| R2-2403153 |
General LCM framework for NW-sided Model |
SHARP Corporation |
| R2-2403160 |
Discussion on functionality based LCM for NW-sided model |
Huawei, HiSilicon |
| R2-2403227 |
Discussion on LCM of Network-Sided Models |
Qualcomm Incorporated |
| R2-2403232 |
LCM for NW-sided model |
Interdigital Inc. |
| R2-2403236 |
Discussion on Functionality-based LCM for NW-side Model |
CEWiT |
| R2-2403458 |
Discussion on LCM for NW-Side Models |
Futurewei Technologies |
| R2-2403570 |
LCM for NW-sided model |
LG Electronics |
| R2-2403590 |
Discussion on LCM for NW sided model |
IIT Kanpur, Indian Institute of Tech (M) |
| R2-2403629 |
LCM for NW-side models |
Ericsson |
| 8.1.2.2 |
LCM for UE-sided model |
|
| R2-2402173 |
LCM for UE-sided model |
OPPO |
| R2-2402251 |
Discussion on LCM for UE-side model |
TCL |
| R2-2402269 |
Discussion on the LCM for UE-sided model |
Fujitsu |
| R2-2402300 |
Discussion on LCM for UE-sided model |
CATT |
| R2-2402340 |
Discussion on LCM for UE-sided model |
Spreadtrum Communications |
| R2-2402365 |
Functionality-based LCM for UE-side Model |
MediaTek Inc. |
| R2-2402420 |
Discussion on LCM for UE-sided model |
Intel Corporation |
| R2-2402430 |
Discussion on LCM for UE-sided model |
Xiaomi |
| R2-2402487 |
Discussion on functionality based LCM for UE-sided model |
vivo |
| R2-2402671 |
LCM for UE sided model |
NEC |
| R2-2402686 |
Discussion on UE-sided model LCM for AI/ML for Air Interface |
HONOR |
| R2-2402730 |
Discussion on LCM for UE-sided model |
Lenovo |
| R2-2402784 |
Functionality-based LCM for UE sided model |
Samsung |
| R2-2402862 |
General LCM framework for UE-sided model |
Apple |
| R2-2402960 |
UE-Side AI/ML Functionality based LCM |
Nokia |
| R2-2403020 |
Discussion on LCM for UE-sided model |
CMCC |
| R2-2403054 |
Some aspects about model inference, monitoring & update for UE side model |
Sony |
| R2-2403096 |
Lifecycle management for UE-sided model |
Fraunhofer HHI, Fraunhofer IIS |
| R2-2403161 |
Discussion on functionality based LCM for UE-sided model |
Huawei, HiSilicon |
| R2-2403166 |
General LCM Framework for UE-sided Model |
SHARP Corporation |
| R2-2403228 |
Discussion on LCM of UE-Sided Models |
Qualcomm Incorporated |
| R2-2403233 |
LCM for UE-sided model |
Interdigital Inc. |
| R2-2403237 |
Discussion on Functionality-based LCM for UE-side Model |
CEWiT |
| R2-2403377 |
Considerations on LCM for UE side Model |
ZTE Corporation,Sanechips |
| R2-2403461 |
Discussion on LCM for UE-Side Models |
Futurewei Technologies |
| R2-2403571 |
LCM for UE-sided model |
LG Electronics |
| R2-2403574 |
Considerations for moving forward with Functionality-based LCM |
Kyocera |
| R2-2403589 |
Discussion on LCM for UE sided model |
IIT Kanpur, Indian Institute of Tech (M) |
| R2-2403656 |
Discussion on LCM for UE side models |
Indian Institute of Tech (M), IIT Kanpur |
| R2-2403662 |
LCM for UE-side models |
Ericsson |
| R2-2403691 |
Discussion LCM for UE-side model |
NTT DOCOMO, INC. |
| 8.1.3 |
NW side data collection |
|
| R2-2402170 |
Data Collection for Network Side Model Training |
OPPO |
| R2-2402252 |
Discussion on NW side data collection |
TCL |
| R2-2402270 |
Discussion on NW side data collection |
Fujitsu |
| R2-2402301 |
Consideration on NW side data collection |
CATT |
| R2-2402341 |
Discussion on NW side data collection |
Spreadtrum Communications |
| R2-2402363 |
Data Collection for Network Side Model Training |
MediaTek Inc. |
| R2-2402421 |
Discussion on network-sided model training data collection |
Intel Corporation |
| R2-2402431 |
Discussion on NW side data collection |
Xiaomi |
| R2-2402488 |
Discussion on NW side data collection |
vivo |
| R2-2402530 |
Discussion on NW side data collection for AI-ML based positioning accuracy enhancement |
Baicells |
| R2-2402594 |
Discussion on data collection for NW-side model training |
NEC |
| R2-2402652 |
Considerations on NW side data collection |
ZTE Corporation |
| R2-2402731 |
Discussion on data collection for NW-sided model |
Lenovo |
| R2-2402776 |
Latency Requirement for Data Collection |
Samsung |
| R2-2402796 |
Network-side data collection |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2402863 |
Discussion on NW-sided data collection |
Apple |
| R2-2402961 |
Data Collection for Training of NW-side AI/ML Models |
Nokia |
| R2-2403021 |
Discussion on NW side data collection |
CMCC |
| R2-2403162 |
Discussion on NW-sided data collection for training |
Huawei, HiSilicon |
| R2-2403229 |
Discussion on Network Side Data Collection |
Qualcomm Incorporated |
| R2-2403234 |
Data Collection for Network-Side Model Training |
Interdigital Inc. |
| R2-2403469 |
Discussion on Data Collection for NW-side Model Training |
Futurewei Technologies |
| R2-2403572 |
NW side data collection |
LG Electronics |
| R2-2403657 |
Discussion on NW side data collection |
Indian Institute of Tech (M), IIT Kanpur |
| R2-2403660 |
NW-side Data Collection |
Ericsson |
| 8.1.4 |
UE side data collection |
|
| R2-2402171 |
Data Collection for UE Side Model Training |
OPPO |
| R2-2402302 |
Consideration on UE side data collection |
CATT |
| R2-2402316 |
Data collection for UE side model training |
Xiaomi |
| R2-2402342 |
Discussion on UE side data collection |
Spreadtrum Communications |
| R2-2402364 |
Data Collection for UE Side Model Training |
MediaTek Inc. |
| R2-2402375 |
Data collection for UE-side model training |
Samsung |
| R2-2402478 |
Label Dataset Transfer for Positioning UE-sided model training |
Intel Corporation |
| R2-2402489 |
Discussion on UE side data collection |
vivo |
| R2-2402669 |
Data Collection for UE side Model training |
NEC |
| R2-2402732 |
Discussion on data collection for UE-sided model |
Lenovo |
| R2-2402864 |
Discussion on UE-sided data collection |
Apple |
| R2-2402962 |
Data Collection for Training of UE-side AI/ML Models |
Nokia |
| R2-2403022 |
Discussion on data collection for UE-sided model training |
CMCC |
| R2-2403122 |
UE-side data collection |
Fraunhofer HHI, Fraunhofer IIS |
| R2-2403163 |
Discussion on UE-sided data collection for training |
Huawei, HiSilicon |
| R2-2403230 |
Discussion on UE Side Data Collection |
Qualcomm Incorporated |
| R2-2403235 |
Data Collection for UE-Side Model Training |
Interdigital Inc. |
| R2-2403378 |
Consideration on UE Side Data Colection |
ZTE Corporation,Sanechips |
| R2-2403473 |
Discussion on Data Collection for UE-side Model Training |
Futurewei Technologies |
| R2-2403492 |
AI/ML Data Collection Requirements |
T-Mobile USA, Verizon, Charter, NTT DOCOMO, Deutsche Telekom, Turkcell, BT, AT&T, Nokia, Telecom Italia, CMCC |
| R2-2403567 |
Discussion on UE side data collection |
China Unicom |
| R2-2403573 |
UE side data collection |
LG Electronics |
| R2-2403658 |
Discussion on UE side data collection |
Indian Institute of Tech (M), IIT Kanpur |
| R2-2403661 |
UE-side Data Collection |
Ericsson |
| R2-2403967 |
Discussion on the definition of different data collection solutions |
Qualcomm |
| 8.2.1 |
Organizational |
|
| R2-2403027 |
Work plan for Ambient IoT |
CMCC, Huawei, T-Mobile |
| R2-2403113 |
TP for TR 38.769 update (RAN2 sub-clause skeleton) |
Huawei, CMCC, T-Mobile USA |
| 8.2.2 |
Stage 2/General aspects |
|
| R2-2402156 |
Discussion on general aspects for Ambient IoT |
China Telecom |
| R2-2402178 |
Stage 2 overall procedures, baseline assumptions on security and use cases |
CATT |
| R2-2402191 |
General considerations on Ambient IoT |
OPPO |
| R2-2402271 |
Discussions on General Aspect of Ambient IoT |
Fujitsu |
| R2-2402323 |
Considerations on the general aspects of the Ambient IOT |
Beijing Xiaomi Software Tech |
| R2-2402349 |
Discussion on general aspects of A-IoT |
Spreadtrum Communications |
| R2-2402374 |
Consideration on general aspects for AIoT |
ZTE Corporation, Sanechips |
| R2-2402392 |
Use Cases and Stage 2 Procedure Flow for Ambient IOT |
InterDigital |
| R2-2402422 |
General considerations for A-IoT |
Intel Corporation |
| R2-2402490 |
General discussion on ambient IoT |
vivo |
| R2-2402696 |
Overall procedure and related aspects on Ambient IoT |
HONOR |
| R2-2402786 |
Principles for RAN2 work on ambient IoT |
MediaTek Inc. |
| R2-2402794 |
Considerations on general aspects for Ambient IoT |
Lenovo |
| R2-2402896 |
A-IoT device hardware capabilities |
Apple |
| R2-2402918 |
General aspects for AIoT |
Samsung |
| R2-2402928 |
Stage-2 and general aspects of Ambient IoT |
Qualcomm Incorporated |
| R2-2402949 |
General aspects for Ambient IoT |
Ericsson |
| R2-2402970 |
Ambient-IoT General Aspects |
NEC |
| R2-2402997 |
General aspects of AIoT |
Nokia |
| R2-2403011 |
General considerations on A-IOT |
CMCC |
| R2-2403055 |
Considerations on various aspects for Ambient IoT |
Sony |
| R2-2403097 |
General aspects, high-level procedure and security aspects for Ambient IoT |
Huawei, HiSilicon, China Telecom, China Unicom, LG Electronics Inc., ZTE Corporation, Sanechips, Apple, NEC |
| R2-2403260 |
Energy-aware design for AIoT daa transmissions |
Nokia |
| R2-2403421 |
Initial consideration of Ambient IoT |
Kyocera |
| R2-2403561 |
Design Targets for Ambient IoT |
T-Mobile USA Inc. |
| R2-2403563 |
LS on Security Requirements for Ambient IoT |
T-Mobile USA Inc. |
| R2-2403609 |
Discussion on general aspects of Ambient IoT |
Futurewei |
| R2-2403676 |
General considerations on Ambient IoT |
Philips International B.V. |
| R2-2403677 |
Discussion on general aspects of ambient IoT |
LG Electronics Inc. |
| R2-2403679 |
Stage 2 overall procedures, baseline assumptions on security and use cases |
CATT, CEPRI |
| 8.2.3.1 |
Control Plane |
|
| R2-2402179 |
Discussion on the Control Plane for Ambient IoT |
CATT |
| R2-2402197 |
Discussion on control-plane aspects for Ambient IoT |
OPPO |
| R2-2402289 |
Control Plane for Ambient-IoT |
NEC Corporation |
| R2-2402322 |
Considerations on the control plane aspects of the Ambient IOT |
Beijing Xiaomi Software Tech |
| R2-2402344 |
Discussion on control plane of Ambient IOT |
Spreadtrum Communications |
| R2-2402376 |
Consideration on CP functionality for AIoT |
ZTE Corporation, Sanechips |
| R2-2402393 |
Control Plane Aspects for Ambient IOT |
InterDigital |
| R2-2402423 |
Required Control plane functions for A-IoT |
Intel Corporation |
| R2-2402491 |
Discussion on Control Plane Aspects for Ambient IoT |
vivo |
| R2-2402793 |
Considerations on C-plane aspects for Ambient IoT |
Lenovo |
| R2-2402891 |
Discussion on Control plane for Ambient IoT |
Apple |
| R2-2402929 |
Control plane aspects of Ambient IoT |
Qualcomm Incorporated |
| R2-2402977 |
Discussion on ambient IoT control plane functionality |
LG Electronics Inc. |
| R2-2403026 |
Discussion on control plane functions and signalling for Ambient IoT |
CMCC |
| R2-2403098 |
Other control plane aspects for Ambient IoT |
Huawei, HiSilicon |
| R2-2403117 |
Discussion on CP aspects of Ambient-IoT |
China Telecom |
| R2-2403406 |
Overview of CP protocols for Ambient IoT |
Ericsson |
| R2-2403516 |
Initial views on the control plane aspects of AIoT |
Samsung Electronics Czech |
| R2-2403611 |
Discussion on Control Plane for Ambient IoT |
NTT DOCOMO INC. |
| R2-2403680 |
Discussion on the Control Plane for Ambient IoT |
CATT, CEPRI |
| 8.2.3.2 |
User Plane |
|
| R2-2402157 |
Discussion on user plane for Ambient IoT |
China Telecom |
| R2-2402165 |
Discussion on protocol stack for ambient IOT |
Xiaomi |
| R2-2402180 |
Discussion on Data Transmission and Protocol Stack of A-IoT |
CATT |
| R2-2402192 |
Discussion on user-plane aspects for Ambient IoT |
OPPO |
| R2-2402272 |
Discussions on User Plane Protocol Stacks |
Fujitsu |
| R2-2402290 |
User Plane for Ambient-IoT |
NEC |
| R2-2402345 |
Discussion on user plane of Ambient IOT |
Spreadtrum Communications |
| R2-2402377 |
Consideration on UP functionality for AIoT |
ZTE Corporation, Sanechips |
| R2-2402394 |
User Plane Aspects for Ambient IOT |
InterDigital |
| R2-2402424 |
Required User plane functions for A-IoT |
Intel Corporation |
| R2-2402492 |
Discussion on User Plane Aspects for Ambient IoT |
vivo |
| R2-2402725 |
Discussion on user plane for Ambient IoT |
Lenovo |
| R2-2402892 |
Discussion on User plane for Ambient IoT |
Apple |
| R2-2402919 |
Initial view on the user plane aspects of AIoT |
Samsung |
| R2-2402938 |
User plane aspects of Ambient IoT |
Qualcomm Incorporated |
| R2-2402950 |
UP protocol and data transmission options |
Ericsson |
| R2-2403012 |
Discussion on User Plane of A-IoT |
CMCC |
| R2-2403099 |
Data transmission and protocol stack for A-IoT |
Huawei, HiSilicon |
| R2-2403259 |
Considerations of the data transmission in AIoT |
Nokia |
| R2-2403349 |
Discussion on user plane protocl stack and data transmission for A-IOT |
LG Electronics Inc. |
| R2-2403372 |
Considerations on protocol architecture for ambient IoT |
KT Corp. |
| R2-2403610 |
Discussion on user plane aspects for Ambient IoT |
Futurewei |
| R2-2403616 |
Discussion on User Plane for Ambient IoT |
NTT DOCOMO INC. |
| R2-2403618 |
Discussion on user plane functionalities in A-IOT |
LG Electronics Inc. |
| R2-2403681 |
Discussion on Data Transmission and Protocol Stack of Ambient IoT |
CATT, CEPRI |
| 8.2.4 |
Paging |
|
| R2-2402181 |
Discussion on Paging Functionality of Ambient IoT |
CATT |
| R2-2402198 |
Discussion on paging procedure for Ambient IoT |
OPPO |
| R2-2402273 |
Discussions on paging |
Fujitsu |
| R2-2402350 |
Discussion on paging functionality of A-IoT |
Spreadtrum Communications |
| R2-2402378 |
Consideration on Paging functionality for AIoT |
ZTE Corporation, Sanechips |
| R2-2402395 |
Paging for Ambient IOT |
InterDigital |
| R2-2402425 |
Paging design for A-IoT |
Intel Corporation |
| R2-2402434 |
Study on Paging for Ambient IoT |
SHARP Corporation |
| R2-2402493 |
Discussion on the functionality of paging in ambient IoT |
vivo |
| R2-2402604 |
Discussion on paging procedure for A-IOT |
Xiaomi |
| R2-2402726 |
Discussion on paging procedure for Ambient IoT |
Lenovo |
| R2-2402893 |
Discussion on Paging for Ambient IoT |
Apple |
| R2-2402930 |
Paging aspects of Ambient IoT |
Qualcomm Incorporated |
| R2-2402971 |
Considerations on Ambient-IoT Paging |
NEC |
| R2-2402978 |
Discussion on ambient IoT paging functionality |
LG Electronics Inc. |
| R2-2403025 |
Discussion on A-IoT paging |
CMCC |
| R2-2403100 |
Discussion on paging-like functionality design |
Huawei, HiSilicon |
| R2-2403115 |
Discussion on paging for Ambient IoT |
China Telecom |
| R2-2403149 |
Consideration on paging in AIoT |
Nokia |
| R2-2403257 |
Ambient IoT Paging Method |
Wiliot Ltd. |
| R2-2403405 |
Discussion on DL reachability for Ambient IoT |
Ericsson |
| R2-2403506 |
Initial considerations on the paging for AIoT |
Samsung |
| R2-2403612 |
Discussion on paging functions for Ambient IoT |
Futurewei |
| R2-2403682 |
Discussion on Paging Functionality of Ambient IoT |
CATT, CEPRI |
| 8.2.5 |
Random Access |
|
| R2-2402158 |
Discussion on random access for Ambient IoT |
China Telecom |
| R2-2402164 |
Discussion on access procedure for ambient IOT |
Xiaomi |
| R2-2402182 |
Discussion on the Random Access for Ambient IoT |
CATT |
| R2-2402200 |
Discussion on random access for Ambient IoT |
OPPO |
| R2-2402274 |
Discussions on Random Access |
Fujitsu |
| R2-2402346 |
Discussion on random access of Ambient IOT |
Spreadtrum Communications |
| R2-2402379 |
Consideration on Random Access procedure for AIoT |
ZTE Corporation, Sanechips |
| R2-2402396 |
Random Access for Ambient IOT |
InterDigital |
| R2-2402426 |
Random access aspects for A-IoT |
Intel Corporation |
| R2-2402435 |
Study on Random access for Ambient IoT |
SHARP Corporation |
| R2-2402494 |
Initial Access Procedure for Ambient IoT |
vivo |
| R2-2402548 |
Discussion on random access for Ambient IoT |
CMCC |
| R2-2402608 |
Discussion on random access for Ambient IoT |
ETRI |
| R2-2402674 |
Initial Access procedure for Ambient IoT device |
NEC |
| R2-2402727 |
Discussion on random access for Ambient IoT |
Lenovo |
| R2-2402894 |
Discussion on Random Access for Ambient IoT |
Apple |
| R2-2402920 |
Initial considerations on the RACH procedure for AIoT |
Samsung |
| R2-2402939 |
Random access aspects of Ambient IoT |
Qualcomm Incorporated |
| R2-2402951 |
Discussion on UL multiple access |
Ericsson |
| R2-2403031 |
Considerations on random access in AIoT |
Nokia |
| R2-2403078 |
Discussion on random access aspects for Ambient-IoT |
Continental Automotive |
| R2-2403114 |
Random access-like procedure for Ambient IoT |
Huawei, HiSilicon |
| R2-2403348 |
Discussion on contention-based access |
LG Electronics Inc. |
| R2-2403613 |
Discussion on random access for Ambient IoT |
Futurewei |
| R2-2403620 |
Discussion on random access for Ambient IoT |
LG Electronics Inc. |
| R2-2403645 |
Discussion on random access for ambient IoT |
Google Inc. |
| R2-2403683 |
Discussion on the Random Access for Ambient IoT |
CATT, CEPRI |
| 8.3 |
AI/ML for Mobility |
|
| R2-2403592 |
AI/ML Mobility |
CEWiT |
| 8.3.1 |
Organizational |
|
| R2-2402167 |
Discussion on work plan of AI mobility SI |
OPPO,MediaTek,Nokia |
| R2-2402332 |
Draft 38.744 TR Skeleton of AI mobility NR |
OPPO |
| 8.3.2 |
RRM measurement prediction |
|
| R2-2402168 |
Discussion on RRM measurement prediction |
OPPO |
| R2-2402250 |
AI/ML RRM measurement prediction |
TCL |
| R2-2402275 |
Discussion on RRM measurement predicton |
Fujitsu |
| R2-2402285 |
Evaluation on Measurement Gap Reduction with AI Prediction |
MediaTek Inc. |
| R2-2402296 |
Evaluation on AI/ML in Spatial/Temporal Prediction for RRM Measurement |
MediaTek Inc. |
| R2-2402303 |
Consideration on RRM measurement prediction |
CATT |
| R2-2402315 |
Artificial Intelligence/Machine Learning for mobility in NR |
BJTU |
| R2-2402343 |
Discussion on RRM measurement prediction |
Spreadtrum Communications |
| R2-2402403 |
Areas of interest for RRM measurement prediction |
Intel Corporation |
| R2-2402410 |
RRM measurement prediction |
Qualcomm Incorporated |
| R2-2402516 |
Discussion on AI/ML based RRM measurement prediction in NR |
China Telecom |
| R2-2402552 |
Initial consideration on RRM measurement prediction |
CMCC |
| R2-2402559 |
Discussion on RRM measurement prediction |
vivo |
| R2-2402589 |
Discussion on RRM measurement prediction |
Samsung |
| R2-2402595 |
Discussion on AI based RRM measurement prediction |
NEC |
| R2-2402687 |
Discussion on AI aided RRM measurement prediction |
HONOR |
| R2-2402733 |
Consideration on types of RRM measurement prediction |
Lenovo |
| R2-2402748 |
Discussion on RRM measurement prediction |
ZTE Corporation |
| R2-2403109 |
Discussion on RRM measurement prediction |
Huawei, HiSilicon |
| R2-2403124 |
RRM measurement prediction |
Fraunhofer HHI, Fraunhofer IIS |
| R2-2403254 |
AI/ML based RRM measurement predictions |
Ericsson |
| R2-2403281 |
On the measurement prediction use-case |
Nokia |
| R2-2403418 |
Potential scenarios for RRM measurement prediction |
Kyocera |
| R2-2403497 |
Consideration on AI/ML based RRM measurement prediction |
Xiaomi |
| R2-2403554 |
RRM measurement prediction |
Interdigital Inc. |
| R2-2403622 |
Cell-level measurement prediction |
LG Electronics Inc. |
| R2-2403670 |
Consideration on RRM measurement prediction |
CATT, Turkcell |
| 8.3.3 |
Measurement event predictions |
|
| R2-2402169 |
Discussion on measurement event prediction |
OPPO |
| R2-2402253 |
Discussion on measurement event prediction |
TCL |
| R2-2402297 |
Evaluation on AI/ML for Measurement Event Prediction |
MediaTek Inc. |
| R2-2402304 |
Consideration on measurement event prediction |
CATT |
| R2-2402317 |
Measurement event prediction |
Xiaomi |
| R2-2402404 |
Areas of interest for measurement event prediction |
Intel Corporation |
| R2-2402411 |
Measurement event predictions |
Qualcomm Incorporated |
| R2-2402560 |
Discussion on Measurement event prediction |
vivo |
| R2-2402590 |
Discussion on measurement event prediction |
Samsung |
| R2-2402683 |
Discussion on measurement event predictions |
III |
| R2-2402688 |
Discussion on AI aided measurement event prediction |
HONOR |
| R2-2402749 |
Discussion on measurement event prediction |
ZTE Corporation |
| R2-2402898 |
On measurement event prediction |
Apple |
| R2-2403023 |
Discussion on measurement event prediction |
CMCC |
| R2-2403056 |
Data collection for event prediction |
Sony |
| R2-2403110 |
Discussion on measurement event prediction |
Huawei, HiSilicon |
| R2-2403214 |
Target scenarios for measurement event prediction |
NEC |
| R2-2403255 |
AI/ML based measurement events prediction |
Ericsson |
| R2-2403282 |
Considerations on the measurement event prediction use-case |
Nokia |
| R2-2403419 |
Potential scenarios for measurement event prediction |
Kyocera |
| R2-2403555 |
Measurement event prediction |
Interdigital Inc. |
| R2-2403623 |
Measurement event prediction |
LG Electronics Inc. |
| R2-2403671 |
Consideration on measurement event prediction |
CATT, Turkcell |
| 8.3.4 |
RLF/HO failure prediction |
|
| R2-2402166 |
Discussion on study on AI/ML for Mobility |
Continental Automotive |
| R2-2402174 |
Discussion on unintended event prediction |
OPPO |
| R2-2402248 |
AI/ML HO failure prediction |
TCL |
| R2-2402249 |
AI/ML RLF prediction |
TCL |
| R2-2402305 |
Consideration on HO Failure and RLF Prediction |
CATT |
| R2-2402405 |
Areas of interest for RLF/HO failure prediction |
Intel Corporation |
| R2-2402412 |
RLF/HO failure prediction |
Qualcomm Incorporated |
| R2-2402432 |
Discussion on RLF/HO failure prediction |
Xiaomi |
| R2-2402561 |
Discussion on RLF/HO failure prediction |
vivo |
| R2-2402689 |
Discussion on HO failure/RLF prediction |
HONOR |
| R2-2402722 |
Prediction for HO failure and RLF |
Lenovo |
| R2-2402750 |
Discussion on RLF and HO failure prediction |
ZTE Corporation |
| R2-2402895 |
On RLF and HO failure prediction |
Apple |
| R2-2402999 |
Discussion on RLF/HOF prediction |
Samsung |
| R2-2403024 |
Discussion on HOF and RLF prediction |
CMCC |
| R2-2403111 |
Discussion on HOF and RLF prediction |
Huawei, HiSilicon |
| R2-2403215 |
Target scenarios for failure prediction |
NEC |
| R2-2403244 |
Discussion on AI/ML based RLF and HOF predictions |
Ericsson |
| R2-2403420 |
Potential scenarios for RLF/HOF prediction |
Kyocera |
| R2-2403452 |
Discussion on HO failure/RLF prediction |
Nokia |
| R2-2403556 |
RLF/HOF prediction |
Interdigital Inc. |
| R2-2403624 |
HOF and RLF prediction |
LG Electronics Inc. |
| R2-2403672 |
Consideration on HO Failure and RLF Prediction |
CATT, Turkcell |
| 8.3.5 |
Simulation assumption and evaluation methodology |
|
| R2-2402175 |
Discussion on simulation assumptions of AI mobility |
OPPO,Nokia,MediaTek,CMCC |
| R2-2402287 |
Discussion on Evaluation Methodology for AI Mobility |
MediaTek Inc. |
| R2-2402306 |
Simulation and evaluation for AIML for mobility in NR |
CATT |
| R2-2402406 |
Simulation Assumption for AI/ML Mobility |
Intel Corporation |
| R2-2402413 |
Simulation assumption and evaluation methodology |
Qualcomm Incorporated |
| R2-2402433 |
Discussion on simulation assumption and evaluvation methodology |
Xiaomi |
| R2-2402445 |
Simulation Environments for AI/ML-assisted Mobility |
Samsung |
| R2-2402553 |
Discussion on common Evaluation Methodology and Simulation Assumption |
CMCC |
| R2-2402562 |
Discussion on Simulation assumption and evaluation methodology |
vivo |
| R2-2402673 |
Simulation assumption and evaluation methodology |
NEC |
| R2-2402751 |
Discussion on simulation assumption and evaulation methodology for AI mobility |
ZTE Corporation |
| R2-2402897 |
On KPIs for evaluation and training datasets |
Apple |
| R2-2403112 |
Discussion on simulation assumptions |
Huawei, HiSilicon |
| R2-2403245 |
Simulation based evaluation of the AIML added mobility |
Ericsson |
| R2-2403487 |
Discussion on simulation assumptions of AI for mobility |
Nokia, Nokia Shanghai Bell |
| R2-2403498 |
Discussion n the simulation assumption and evaluation methodology of AI/ML for mobility |
NTT DOCOMO, INC. |
| R2-2403514 |
Discussions on simulation assumption and evaluation methodology |
KDDI Corporation |
| R2-2403557 |
Simulation assumption and evaluation methodology |
Interdigital Inc. |
| R2-2403568 |
Discussion on simulation assumption of AI for mobility |
China Unicom |
| R2-2403673 |
Simulation and evaluation for AIML for mobility in NR |
CATT, Turkcell |
| R2-2403713 |
Discussion on simulation assumptions of AI mobility |
OPPO, Nokia, MediaTek, CMCC, InterDigital |
| R2-2403958 |
Views on evaluation scenarios for AI mobility NR |
OPPO, MediaTek, Samsung,CMCC, Nokia, CAICT, CATT, Xiaomi, China Telcom, vivo |
| R2-2404026 |
[Simulation assumptions and methodology] |
OPPO |
| 8.4.1 |
Organizational |
|
| R2-2402635 |
Work plan for Rel-19 WI on LP-WUSWUR |
vivo (Rapporteur) |
| 8.4.2 |
Procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE |
|
| R2-2402159 |
Views on procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE |
China Telecom |
| R2-2402194 |
Discussion on procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE |
OPPO |
| R2-2402320 |
Discussion on LP-WUS/WUR for RRC IDLE/INACTIVE state |
KT Corp. |
| R2-2402347 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
Spreadtrum Communications |
| R2-2402446 |
General considerations on the procedure for RRC_IDLE_INACTIVE |
Xiaomi Communications |
| R2-2402539 |
Analysis on Procedure and Configuration of LP-WUS for IDLE/INACTIVE Modes |
CATT |
| R2-2402592 |
Discussion on procedure of LP-WUS in RRC_IDLE INACITVE |
NEC |
| R2-2402597 |
Discussion on entry exit conditions for LP-WUS monitoring |
Sharp |
| R2-2402624 |
Discussion on LP-WUS WUR in RRC_IDLE INACTIVE |
vivo |
| R2-2402690 |
Overall procedure of LP-WUS in RRC_IDLE/INACTIVE |
HONOR |
| R2-2402754 |
Procedure and configuration of LP-WUS for IDLE and INACTIVE modes |
ZTE Corporation, Sanechips |
| R2-2402875 |
Procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE |
Apple |
| R2-2402933 |
Procedure and Configuration of LP-WUS in RRC Idle Inactive Mode |
Samsung |
| R2-2402963 |
Discussion on procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE |
Huawei, HiSilicon |
| R2-2402972 |
Procedure and configuration of LP-WUS |
LG Electronics Inc. |
| R2-2403028 |
LP-WUS operation in IDLE INACTIVE modes |
CMCC |
| R2-2403037 |
Low Power Receiver: First points to address |
Vodafone |
| R2-2403043 |
Procedure and Configuration of LP-WUS in RRC IDLE/INACTIVE |
Lenovo |
| R2-2403057 |
RAN2 aspects on LP-WUS/WUR in RRC Idle/Inactive mode |
Sony |
| R2-2403135 |
LP-WUS based paging |
Qualcomm Incorporated |
| R2-2403272 |
LP-WUS in IDLE and INACTIVE |
Nokia |
| R2-2403332 |
Discussion on Procedure and configuration in RRC_IDLE/INACTIVE |
NTT DOCOMO INC.. |
| R2-2403333 |
Discussion on LP-WUS operation in RRC_IDLE/INACTIVE modes |
InterDigital, Inc. |
| R2-2403550 |
WUR in Idle and Inactive |
Ericsson |
| R2-2403551 |
WUR and RRM measurements |
Ericsson |
| R2-2403698 |
Procedure and configuration of LP-WUS in RRC_IDLE and RRC_INACTIVE |
Apple |
| 8.4.3 |
RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
|
| R2-2402201 |
Discussion on RRM measurement in RRC IDLE and INACTIVE |
OPPO |
| R2-2402348 |
Discussion on RRM measurement relaxation and offloading in IDLE/INACTIVE mode |
Spreadtrum Communications |
| R2-2402447 |
RRM measurement relaxation for RRC_IDLE_INACTIVE |
Xiaomi Communications |
| R2-2402477 |
Discussion on RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
Huawei, HiSilicon |
| R2-2402540 |
RRM Relaxation and Offloading in RRC_IDLE/INACTIVE |
CATT |
| R2-2402593 |
Discussion on RRM measurement for LP-WUS in RRC_IDLE INACTIVE |
NEC |
| R2-2402598 |
Discussion on serving cell RRM measurement offloading |
Sharp |
| R2-2402625 |
Discussion on RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
vivo |
| R2-2402728 |
RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
Lenovo |
| R2-2402755 |
RRM measurement relaxation for IDLEINACTIVE modes |
ZTE Corporation, Sanechips |
| R2-2402876 |
RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
Apple |
| R2-2402934 |
RRM measurement relaxation and offloading in RRC Idle Inactive Mode |
Samsung |
| R2-2402973 |
RRM Measurement offloading to LR |
LG Electronics Inc. |
| R2-2403029 |
Discussion on LP-WUR measurement offloading in IDLE INACTIVE modes |
CMCC |
| R2-2403058 |
Discussion on RRMRAN2 aspects foron LP-WUS/WUR |
Sony |
| R2-2403116 |
Discussion on RRM measurement relaxation in RRC_IDLE/INACTIVE |
China Telecom |
| R2-2403136 |
LP-WUS RRM measurement relaxation and offloading |
Qualcomm Incorporated |
| R2-2403273 |
RRM measurement relaxation in RRC_IDLE/INACTIVE |
Nokia |
| R2-2403699 |
RRM measurement relaxation and offloading in RRC_IDLE and RRC_INACTIVE |
Apple |
| 8.4.4 |
Procedures for LP-WUS in RRC_CONNECTED |
|
| R2-2403059 |
Considerations on LP-WUS/WUR in RRC Connected mode |
Sony |
| R2-2403334 |
Discussion on LP-WUS operation in RRC_CONNECTED mode |
InterDigital, Inc. |
| R2-2403696 |
Discussion on LP-WUS WUR in RRC_Connected |
vivo |
| 8.5.1 |
Organizational |
|
| R2-2402857 |
Updated Workplan for Rel-19 network energy savings WI |
Rapporteurs (Ericsson, Apple) |
| 8.5.2 |
On-demand SSB SCell operation |
|
| R2-2402150 |
Initial discussion about on-demand SSB SCell operation |
China Telecom |
| R2-2402230 |
Discussion on On-Demand SSB |
OPPO |
| R2-2402351 |
Discussion on on-demand SSB SCell operation |
Spreadtrum Communications |
| R2-2402370 |
On-demand SSB SCell Operation |
Samsung Electronics Co., Ltd |
| R2-2402397 |
Areas of interest for on-demand SSB SCell operation |
Intel Corporation |
| R2-2402568 |
Discussion on on-demand SSB SCell operation |
vivo |
| R2-2402599 |
Discussion on on-demand SSB procedure |
Quectel |
| R2-2402603 |
Discussion on on-demand SSB |
Xiaomi |
| R2-2402637 |
Consideration on on-demand SSB SCell operation in connected mode |
ZTE Corporation, Sanechips |
| R2-2402658 |
Consideration on on-demand SSB SCell operation |
CATT |
| R2-2402737 |
Discussion on On-demand SSB SCell operation |
Lenovo |
| R2-2402823 |
Discussion on on-demand SSB SCell operation for NES |
Huawei, HiSilicon |
| R2-2402858 |
Discussion on RAN2 work of on-demand SSB for SCell |
Apple |
| R2-2402912 |
On-demand SSB SCell Operation |
InterDigital |
| R2-2402974 |
On-demand SSB SCell operation |
LG Electronics Inc. |
| R2-2403015 |
Discussion on on-demand SSB SCell operation |
CMCC |
| R2-2403060 |
On-demand SSB Scell operation discussion |
Sony |
| R2-2403195 |
Discussion on On-demand SSB |
Qualcomm Incorporated |
| R2-2403216 |
Discussion on On-demand SSB for SCell |
NEC |
| R2-2403359 |
Consideration on on-demand SSB SCell operation |
Fujitsu |
| R2-2403402 |
Discussion on on-demand SSB for NES |
Ericsson |
| R2-2403599 |
On demand SSB handling |
Nokia, Nokia Shanghai Bell |
| 8.5.3 |
On-demand SIB1 |
|
| R2-2402151 |
Initial discussion about on-demand SIB1 |
China Telecom |
| R2-2402162 |
Discussion on on-demand SIB1 |
Xiaomi |
| R2-2402369 |
On-demand SIB1 |
Samsung Electronics Co., Ltd |
| R2-2402398 |
Areas of interest for on-demand SIB1 operation |
Intel Corporation |
| R2-2402569 |
Discussion on on-demand SIB1 for RRC IDLE and INACTIVE UE |
vivo |
| R2-2402638 |
Consideration on on-demand SIB1 in idle and inactive mode |
ZTE Corporation, Sanechips |
| R2-2402659 |
Consideration on on-demand SIB1 |
CATT |
| R2-2402661 |
On-demand SIB1 for Idle/Inactive mode UEs |
III |
| R2-2402691 |
Discussion on on-demand SIB1 for NES |
HONOR |
| R2-2402782 |
Discussion on on-demand SIB1 operation for NES |
Huawei, HiSilicon |
| R2-2402859 |
Discussion on RAN2 work of on-demand SIB1 |
Apple |
| R2-2402911 |
On-demand SIB1 for NES |
InterDigital |
| R2-2402969 |
Discussion on on-demand SIB1 transmission for network energy savings |
Fujitsu |
| R2-2402975 |
On-demand transmission of SIB1 |
LG Electronics Inc. |
| R2-2403001 |
On demand SIB1 terminologies and scenarios |
Lenovo |
| R2-2403003 |
On-demand SIB1 for NES |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2403016 |
Discussion on on-demand SIB1 |
CMCC |
| R2-2403041 |
Views on On-demand SIB1 operation for idle/inactive UEs |
Vodafone |
| R2-2403061 |
UL WUS for on-demand SIB1 |
Sony |
| R2-2403062 |
On-demand SIB1 for IDLE/INACTIVE UEs |
Sony |
| R2-2403080 |
Discussion on the on-demand SIB1 transmission |
Google Inc. |
| R2-2403132 |
Consideration on on-demand SIB1 |
OPPO |
| R2-2403202 |
Discussion on On-demand SIB1 |
Qualcomm Incorporated |
| R2-2403217 |
Discussion on On-demand SIB1 for Idle/Inactive |
NEC |
| R2-2403403 |
Discussion on on-demand SIB1 for NES |
Ericsson |
| R2-2403426 |
On demand SIB1 for idle/inactive UE |
KDDI Corporation |
| R2-2403600 |
On demand SIB1 handling |
Nokia, Nokia Shanghai Bell |
| 8.5.4 |
Adaptation of common signal/channel transmissions |
|
| R2-2402163 |
Discussion on common signal adaptation |
Xiaomi |
| R2-2402276 |
Adaptation of common signal or channel |
Fujitsu |
| R2-2402326 |
Discussion on adaptation of common signal/channel transmissions |
OPPO |
| R2-2402352 |
Discussion on adaptation of common signal/channel transmissions |
Spreadtrum Communications |
| R2-2402371 |
Adaptation of common signal/channel transmissions |
Samsung Electronics Co., Ltd |
| R2-2402399 |
Areas of interest for adaptation of common signal/channel transmission |
Intel Corporation |
| R2-2402570 |
Discussion on adaptation on common signal transmissions |
vivo |
| R2-2402639 |
Consideration on paging occasion adaptation |
ZTE Corporation, Sanechips |
| R2-2402660 |
Consideration on adaptation of common signal channel transmissions |
CATT |
| R2-2402672 |
RAN2 impact of adaptation of common channel transmissions |
NEC |
| R2-2402692 |
Discussion on adaptation of common signal/channel transmissions |
HONOR |
| R2-2402738 |
Paging and PRACH adaptation for NES operation |
Lenovo |
| R2-2402824 |
Discussion on adaptation of common signal/channels transmissions |
Huawei, HiSilicon |
| R2-2402860 |
Discussion on RAN2 work of common signal transmission adaptation |
Apple |
| R2-2402910 |
Time domain adaptation of common signalling and channels |
InterDigital |
| R2-2403002 |
Adaptation of Common Signals and Channels for NES |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2403017 |
Discussion on adaptation of common signal/channel transmissions |
CMCC |
| R2-2403204 |
Discussion on Adaptation of Common Signal and Channel Transmissions |
Qualcomm Incorporated |
| R2-2403404 |
Adaptation of common signal/channel transmissions for NES |
Ericsson |
| R2-2403427 |
Discussion on adaptation of common signal/channel transmissions |
III |
| R2-2403521 |
Discussion on common signal and channel adaptation |
LG Electronics Inc. |
| R2-2403601 |
Common signal aspects of NES WI |
Nokia, Nokia Shanghai Bell |
| 8.6.1 |
Organizational |
|
| R2-2402906 |
Work plan for Rel-19 Further NR Mobility Enhancements (rapp) |
Apple, China Telecom |
| 8.6.2 |
Inter-CU LTM |
|
| R2-2402176 |
Discussion on inter-CU LTM |
CATT |
| R2-2402291 |
Inter-CU LTM discussion |
MediaTek inc. |
| R2-2402337 |
Discussion on Inter-CU LTM |
Spreadtrum Communications |
| R2-2402361 |
Discussion on inter-CU LTM |
KDDI Corporation |
| R2-2402407 |
Inter-CU LTM supported scenarios |
Intel Corporation |
| R2-2402408 |
Inter-CU LTM security handling |
Intel Corporation |
| R2-2402441 |
Discussion on inter-CU LTM |
OPPO |
| R2-2402452 |
Discussion on supporting Inter-CU LTM cell switch |
Transsion Holdings |
| R2-2402531 |
Discussion on Inter-CU LTM |
China Telecom |
| R2-2402626 |
Discussion on inter-CU LTM |
vivo |
| R2-2402697 |
Discussion on inter-CU LTM |
HONOR |
| R2-2402724 |
Discussion on Inter-CU LTM |
Lenovo |
| R2-2402742 |
Discussion on inter-CU LTM |
ZTE Corporation |
| R2-2402907 |
Important topics for inter-CU LTM |
Apple |
| R2-2402925 |
Discussion on inter-gNB LTM |
Qualcomm Incorporated |
| R2-2402926 |
Inter-gNB LTM and UE context relocation |
Qualcomm Incorporated |
| R2-2402976 |
On subsequent cell switch for inter-CU LTM |
Panasonic |
| R2-2402982 |
Initial Considerations to Support Inter-CU LTM |
Samsung |
| R2-2403018 |
Initial Considerations on Inter-CU LTM |
CMCC |
| R2-2403033 |
Discussion on inter-CU LTM |
LG Electronics |
| R2-2403063 |
LTM for Inter-CU |
Sony |
| R2-2403207 |
Discussion on Inter-CU LTM |
Interdigital, Inc. |
| R2-2403209 |
Discussion on inter-CU LTM |
Langbo |
| R2-2403218 |
Discussion on challenges for inter-CU LTM |
NEC |
| R2-2403238 |
LTM Enhancements for Inter-CU mobility |
CEWiT |
| R2-2403277 |
Initial considerations for inter-CU LTM |
Ericsson |
| R2-2403283 |
Considerations on Inter-CU LTM |
Nokia |
| R2-2403290 |
Inter-CU LTM |
Huawei, HiSilicon |
| R2-2403422 |
Initial consideration on inter-CU LTM |
Kyocera |
| R2-2403496 |
Discussion on Inter-CU LTM |
Xiaomi |
| R2-2403503 |
Discussion on Inter-CU mobility procedure |
ETRI |
| R2-2403511 |
Discussion on potential issues for supporting inter-CU LTM |
Sharp |
| R2-2403520 |
Discussion on inter-CU LTM |
Fujitsu |
| R2-2403582 |
Discussion on inter-CU LTM |
ITL |
| R2-2403621 |
Discussion on inter-CU LTM |
DENSO CORPORATION |
| R2-2403684 |
Discussion on inter-CU LTM |
NTT DOCOMO, INC. |
| R2-2403929 |
[Draft] LS on security handling for inter-CU LTM in non-DC cases |
Apple |
| R2-2404037 |
LS on security handling for inter-CU LTM in non-DC cases |
RAN2 |
| 8.6.3 |
Measurement enhancements for LTM |
|
| R2-2402177 |
Consideration on Event triggered L1 measurement reporting |
CATT |
| R2-2402277 |
Measurement enhancements for LTM |
Fujitsu |
| R2-2402292 |
Initial discussion on event-triggered L1 measurement reporting |
MediaTek inc. |
| R2-2402338 |
Discussion on measurement enhancements for LTM |
Spreadtrum Communications |
| R2-2402442 |
Event triggered L1 measurement report |
OPPO |
| R2-2402453 |
Discussion on measurement enhancement for LTM |
Transsion Holdings |
| R2-2402532 |
Discussion on event-triggered L1 measurement reporting for LTM |
China Telecom |
| R2-2402627 |
Discussion on measurement enhancement for LTM |
vivo |
| R2-2402698 |
Discussion on L1 measurement enhancement |
HONOR |
| R2-2402743 |
Discussion on event-triggered L1 measurement reporting |
ZTE Corporation |
| R2-2402847 |
Discussion on event-triggered L1 measurement reporting |
Xiaomi |
| R2-2402877 |
Measurement enhancements for LTM |
Apple |
| R2-2402983 |
Support of Event-Triggered L1 Measurement Enhancements for LTM |
Samsung |
| R2-2403030 |
Discussion on LTM measurement related enhancements |
CMCC |
| R2-2403181 |
Discussion on initial aspects for event triggered L1 measurements |
Ericsson |
| R2-2403208 |
Event triggered L1 reporting for LTM |
Interdigital, Inc. |
| R2-2403219 |
Discussion on event-triggered L1 measurement reporting |
NEC |
| R2-2403291 |
Event triggered L1 report for LTM |
Huawei, HiSilicon |
| R2-2403305 |
On Measurement-related Enhancements for Rel-19 LTM |
Nokia |
| R2-2403423 |
Initial consideration on event-triggered L1 measurement reporting |
Kyocera |
| R2-2403509 |
Discussions on Event-triggered L1 measurement reporting |
KDDI Corporation |
| R2-2403512 |
Discussion on event triggered L1 measurement report |
Sharp |
| R2-2403581 |
Discussion on measurement enhancements for LTM |
ITL |
| R2-2403643 |
Measurement related enhancements for LTM |
LG Electronics Inc. |
| 8.7.1 |
Organizational |
|
| R2-2402836 |
XR Workplan |
Nokia, Qualcomm (Rapporteurs) |
| R2-2402837 |
SA2 Overview |
Nokia, Qualcomm (Rapporteurs) |
| R2-2402838 |
Multi-Modal Communication Overview |
Nokia, Qualcomm (Rapporteurs) |
| 8.7.2 |
Multi-modality support |
|
| R2-2402278 |
Discussions on Multi-modality Awareness |
Fujitsu |
| R2-2402353 |
Discussion on XR Multi-modality |
Spreadtrum Communications |
| R2-2402400 |
Justification and areas of interest for Multi-modal Services |
Intel Corporation |
| R2-2402443 |
Multi-Modality Support in RAN |
Samsung |
| R2-2402474 |
Discussion on multi-modal XR |
Huawei, HiSilicon |
| R2-2402510 |
Initial Consideration on Multi-Modality |
CATT |
| R2-2402549 |
Discussion on multi-modality support for XR |
CMCC, CSPG |
| R2-2402628 |
Discussion on Multi-modality |
vivo |
| R2-2402676 |
Discussion on Multi-modality support for XR traffic |
Xiaomi Communications |
| R2-2402762 |
RAN enhancements for Multi-Modality support |
ZTE Corporation, Sanechips |
| R2-2402841 |
Discussion on Multi-modal support for XR |
LG Electronics Inc. |
| R2-2402879 |
Views on Support of Multi-Modality Services in Rel-19 XR |
Apple |
| R2-2402953 |
Support of Multi-Modal XR applications |
Lenovo |
| R2-2402979 |
Discussion on Multi-Modality XR |
Meta |
| R2-2403064 |
XR multi modal flows |
Sony |
| R2-2403091 |
Discussion on Multi-modality support for XR |
TCL |
| R2-2403118 |
Discussion on multi-modality enhancement for XR traffic |
China Telecom |
| R2-2403133 |
Discussion on the multi-modality support |
OPPO |
| R2-2403223 |
Discussion on multi-modality |
Ericsson |
| R2-2403294 |
Multi-modality support for XR |
InterDigital |
| R2-2403407 |
Discussion on multi-modality support |
NEC Corporation |
| R2-2403411 |
Multi-modality work in Rel-19 |
Nokia, Nokia Shanghai Bell |
| R2-2403569 |
Consideration on RAN enhancements for Multi-Modality |
China Unicom |
| R2-2403659 |
Multi-modality support for XR |
Google Inc. |
| R2-2403674 |
Discussion on multi-modality |
MediaTek Inc. |
| 8.7.4 |
Scheduling enhancements |
|
| R2-2402314 |
Discussion on Scheduling enhancements in XR |
TCL |
| R2-2402325 |
Discussion on scheduling enhancements for XR |
OPPO |
| R2-2402339 |
Discussion on XR scheduling enhancement |
Spreadtrum Communications |
| R2-2402389 |
Discussion on delay-aware scheduling |
Qualcomm Incorporated |
| R2-2402401 |
Areas of interest for UL scheduling enhancements of XR traffic |
Intel Corporation |
| R2-2402444 |
Scheduling Enhancements for Delay-Critical Data Transmission |
Samsung |
| R2-2402511 |
Consideration on XR specific scheduling enhancement |
CATT |
| R2-2402550 |
Discussion on scheduling enhancement for XR |
CMCC |
| R2-2402629 |
Discussion on scheduling enhancement for XR |
vivo |
| R2-2402675 |
Discussion on scheduling enhancements of XR traffic |
Xiaomi Communications |
| R2-2402684 |
Discussion on delay-based UL scheduling enhancements |
HONOR |
| R2-2402763 |
Scheduling enhancements for XR |
ZTE Corporation, Sanechips |
| R2-2402880 |
Views on Delay-Aware Operations in Rel-19 XR |
Apple |
| R2-2402952 |
Enhanced Uplink Scheduling for XR |
Lenovo |
| R2-2402980 |
Discussion on Scheduling Enhancement for XR |
Meta |
| R2-2403045 |
Considerations on delay-sensitive scheduling for XR |
NEC Corporation |
| R2-2403052 |
Scheduling Enhancements for XR |
Nokia, Nokia Shanghai Bell |
| R2-2403065 |
UL Scheduling enhancements for XR |
Sony |
| R2-2403119 |
Discussion on scheduling enhancements for XR traffic |
China Telecom |
| R2-2403143 |
Delay-aware scheduling enhancements |
Huawei, HiSilicon |
| R2-2403225 |
UL scheduling enhancements |
Ericsson |
| R2-2403295 |
Scheduling enhancements for XR |
InterDigital |
| R2-2403415 |
Discussion for scheduling enhancements |
III |
| R2-2403591 |
Discussion on UL scheduling enhancements |
MediaTek Inc. |
| R2-2403626 |
Discussion on resource allocation for XR |
Google Inc. |
| R2-2403669 |
Discussion on scheduling enhancement for XR |
LG Electronics Inc. |
| R2-2403690 |
UL related Scheduling Enhancements for XR |
Rakuten Mobile, Inc |
| 8.7.5 |
RLC enhancements |
|
| R2-2402212 |
Discussion on RLC re-transmission related enhancements |
OPPO |
| R2-2402254 |
RLC re-transmission enhancements for XR |
ITRI |
| R2-2402279 |
Discussions on RLC enhancements |
Fujitsu |
| R2-2402318 |
RLC AM retransmission enhancements |
Xiaomi |
| R2-2402354 |
Discussion on RLC enhancements for XR |
Spreadtrum Communications |
| R2-2402390 |
Discussion on RLC enhancements |
Qualcomm Incorporated |
| R2-2402402 |
RLC AM retransmission enhancements |
Intel Corporation |
| R2-2402512 |
Consideration on RLC Retransmission Enhancement for XR |
CATT |
| R2-2402515 |
Discussion on RLC AM enhancements |
Huawei, HiSilicon |
| R2-2402573 |
Discussion on RLC enhancements in XR |
CMCC |
| R2-2402630 |
Discussion on RLC enhancement for XR |
vivo |
| R2-2402685 |
Discussion on RLC enhancements for XR |
HONOR |
| R2-2402699 |
Considerations on RLC re-transmission related enhancements for XR |
KDDI Corporation |
| R2-2402734 |
AM RLC enhancement |
Lenovo |
| R2-2402764 |
RLC enhancements for XR |
ZTE Corporation, Sanechips |
| R2-2402817 |
RLC AM enhancement |
NEC |
| R2-2402839 |
RLC Enhancements for XR |
Nokia |
| R2-2402881 |
Views on RLC-AM Enhancements for Rel-19 XR |
Apple |
| R2-2402981 |
Discussion on RLC Enhancements for XR |
Meta |
| R2-2403090 |
RLC AM retransmission enhancement for XR |
TCL |
| R2-2403102 |
Discussion on RLC enhancements on small packet delay budget scenario |
MediaTek Inc. |
| R2-2403296 |
RLC enhancements for XR |
InterDigital |
| R2-2403368 |
Discussion on RLC AM Enhancements |
Ericsson |
| R2-2403462 |
Consideration on RLC enhancements for XR |
LG Electronics Inc. |
| R2-2403504 |
Discussion on RLC enhancements for XR |
Samsung |
| R2-2403675 |
Discussion on RLC Retransmission Enhancements for XR |
Rakuten Mobile, Inc |
| 8.8.1 |
Organizational |
|
| R2-2402357 |
Work plan for Rel-19 NR_NTN_Ph3 |
CATT, Thales |
| R2-2403638 |
NR NTN phase 3 scope |
Ericsson |
| 8.8.2 |
Downlink coverage enhancements |
|
| R2-2402219 |
RAN2 Aspects For Downlink Coverage Enhancements |
vivo |
| R2-2402547 |
Downlink coverage enhancement for NR NTN |
CMCC,CSPG |
| R2-2402702 |
Discussion on downlink coverage enhancements for NTN |
Xiaomi |
| R2-2402712 |
Network energy saving for downlink coverage enhancement in NTN |
Lenovo |
| R2-2402805 |
Downlink Coverage Enhancement |
Samsung |
| R2-2402825 |
Discussion on downlink coverage enhancements |
Huawei, HiSilicon, Turkcell |
| R2-2402883 |
DL coverage enhancement in NTN |
Apple |
| R2-2403034 |
DL coverage enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2403071 |
Consideration on downlink coverage enhancements |
ZTE Corporation, Sanechips |
| R2-2403276 |
Discussion on RAN2 Aspects for Downlink Coverage Enhancements in NR NTN evolution |
THALES |
| R2-2403319 |
Downlink coverage enhancement for NTN |
InterDigital |
| R2-2403649 |
Discussion for DL coverage enhancement |
Sharp |
| 8.8.4 |
Support of Broadcast service |
|
| R2-2402152 |
Signaling of indicating service area in NR NTN |
China Telecom |
| R2-2402199 |
Discussion on providing MBS service area in NTN network |
OPPO |
| R2-2402220 |
Discussion on MBS Broadcast Provision in NTN |
vivo |
| R2-2402280 |
Discussions on signaling of the intended service area of a broadcast service |
Fujitsu |
| R2-2402284 |
Discussion on the support of broadcast service in NTN |
ETRI |
| R2-2402355 |
Discussion on support of broadcast service via NR NTN |
CATT, China Broadnet |
| R2-2402544 |
Discussion on MBS broadcast enhancements for NTN |
CMCC |
| R2-2402695 |
Discussion on the support of Broadcast service |
HONOR |
| R2-2402708 |
Discussion on MBS service in NTN system |
CAICT |
| R2-2402713 |
On support of MBS broadcast in NTN |
Lenovo |
| R2-2402806 |
MBS Broadcast Service Area in NTN |
Samsung |
| R2-2402807 |
MBS broadcast service area information |
Qualcomm Incorporated |
| R2-2402826 |
Discussion on MBS over NTN |
Huawei, HiSilicon, Turkcell |
| R2-2402833 |
Discussion on the service area of a broadcast service |
Xiaomi |
| R2-2402884 |
Broadcast service support over NTN |
Apple |
| R2-2403072 |
Consideration on broadcast service enhancements |
ZTE Corporation, Sanechips |
| R2-2403093 |
Discussion on MBS Broadcasting Control over NTN access |
TCL |
| R2-2403121 |
Discussion on support of broadcast service in NTN |
LG Electronics France |
| R2-2403275 |
Discussion on MBS broadcast additional features for NR NTN Evolution |
THALES |
| R2-2403306 |
On MBS Service Area Signalling in Rel-19 NTN |
Nokia |
| R2-2403320 |
Support for broadcast service in NTN |
InterDigital |
| R2-2403587 |
Discussion on support of broadcast service |
ITL |
| R2-2403648 |
Discussion on Intended Service Area for NTN-MBS |
NTT DOCOMO INC. |
| R2-2403650 |
Discussion on MBS service support for NR NTN |
Sharp |
| 8.8.5 |
Support of regenerative payload |
|
| R2-2402153 |
Stage-2 impact of regenerative payload in NR NTN |
China Telecom |
| R2-2402196 |
Discussion on stage-2 update on the support of regenerative payload |
OPPO |
| R2-2402356 |
Discussion on support of regenerative payload in Rel-19 NR NTN |
CATT, China Broadnet |
| R2-2402714 |
On support of regenerative payload in NTN |
Lenovo |
| R2-2402808 |
Discussion on regenerative payload |
Qualcomm Incorporated |
| R2-2402818 |
Support of regenerative payload |
NEC |
| R2-2403092 |
Discussion on Regenerative NTN Architecture |
TCL |
| R2-2403409 |
Discussion on Regenerative NTN Payload Architecture |
TCL |
| R2-2403606 |
Regenerative NTN payload support in NR NTN Evolution |
THALES, CATT, Huawei, ZTE, Inmarsat, Viasat |
| R2-2403639 |
Stage 2 updates for regenerative payload |
Ericsson |
| 8.8.6 |
LTE to NR NTN mobility |
|
| R2-2402154 |
Support of LTE TN to NR NTN mobility |
China Telecom |
| R2-2402195 |
Discussion on LTE to NR NTN idle mode mobility |
OPPO |
| R2-2402221 |
Discussion on LTE TN to NR NTN Mobility |
vivo |
| R2-2402545 |
Discussion on idle mode mobility enhancements for E-UTRAN TN to NR-NTN |
CMCC |
| R2-2402809 |
Idle mode mobility from LTE to NR NTN |
Qualcomm Incorporated |
| R2-2402827 |
Discussion on LTE TN to NR NTN mobility |
Huawei, HiSilicon, Turkcell |
| R2-2402834 |
Discussion on the cell reselection from LTE to NR NTN |
Xiaomi |
| R2-2402885 |
Mobility from LTE TN to NR NTN |
Apple |
| R2-2403035 |
Support of Idle Mode Mobility from EUTRA TN to NR NTN |
CATT |
| R2-2403066 |
Support for LTE to NR-NTN idle mode mobility |
Telit Communications S.p.A. ; Thales |
| R2-2403073 |
Consideration on idle mode mobility between LTE TN and NR NTN |
ZTE Corporation, Sanechips |
| R2-2403123 |
Discussion on support of LTE to NR NTN cell reselection |
LG Electronics France |
| R2-2403205 |
Discussion on LTE to NR NTN mobility |
Interdigital, Inc. |
| R2-2403226 |
Discussion on cell reselection from E-UTRA TN to NR NTN |
MediaTek Inc. |
| R2-2403307 |
On E-UTRA TN to NR NTN Mobility in IDLE mode |
Nokia |
| R2-2403339 |
E-UTRAN TN to NR NTN mobility |
Samsung |
| R2-2403640 |
E-UTRAN TN to NR-NTN mobility |
Ericsson |
| 8.9.1 |
Organizational |
|
| R2-2402941 |
Work Plan for Rel-19 IoT NTN |
MediaTek Inc. |
| R2-2403641 |
IoT NTN phase 3 scope |
Ericsson |
| 8.9.2 |
Support of Store & Forward |
|
| R2-2402155 |
The consideration of supporting Store & Forward in IoT NTN |
China Telecom |
| R2-2402193 |
Discussion on Store & Forward satellite operation |
OPPO |
| R2-2402222 |
RAN2 Aspects For Store & Forward |
vivo |
| R2-2402380 |
RAN2 impacts of supporting Store&Forward operation in IoT NTN |
ZTE Corporation, Sanechips |
| R2-2402454 |
Discussion on support of Store&Forward |
Transsion Holdings |
| R2-2402475 |
Overview of the Store and Forward satellite operation |
Huawei, HiSilicon, Turkcell |
| R2-2402541 |
Discussion on IoT NTN Store and Forward |
CMCC |
| R2-2402693 |
Discussion on Store and Forward operations in IoT-NTN |
HONOR |
| R2-2402710 |
Discussion on Store & Forward satellite operation IoT NTN |
CAICT |
| R2-2402715 |
On support of Store and Forward operations in NTN |
Lenovo |
| R2-2402810 |
S&F satellite operation with full eNB as regenerative payload |
Qualcomm Incorporated |
| R2-2402819 |
Support of Store and Forward |
NEC |
| R2-2402821 |
Considerations on Store & Forward Satellite Operation |
SHARP Corporation |
| R2-2402835 |
Initial views on the support of store and forward satellite operation |
Xiaomi |
| R2-2402886 |
Support of S&F operation in IoT NTN |
Apple |
| R2-2402942 |
RAN2 impact on S&F mode |
MediaTek Inc. |
| R2-2403044 |
Discussion on support of store and forward operation |
CATT |
| R2-2403148 |
Radio Interface Imapcts for Store-Forward mode operation of IoT-NTN |
Nokia, Nokia Shanghai Bell |
| R2-2403274 |
Discussion on Store and Forward support for IoT NTN Phase 3 |
THALES |
| R2-2403321 |
Support for Store and Forward operation in NTN |
InterDigital |
| R2-2403337 |
On RAN2 aspects of Store and Forward |
Samsung |
| R2-2403689 |
RAN aspects of S&F operation for IoT NTN |
Sateliot |
| 8.9.3 |
Uplink Capacity Enhancement |
|
| R2-2402202 |
Discussion on enhanced EDT for IoT NTN |
OPPO |
| R2-2402223 |
Discussion on EDT Enhancement for IoT-NTN |
vivo |
| R2-2402336 |
Uplink Capacity Enhancement for EDT transaction |
Spreadtrum Communications |
| R2-2402381 |
Consideration on enhanced early data transmission in IoT NTN |
ZTE Corporation, Sanechips |
| R2-2402476 |
Overview of capacity enhancement for uplink |
Huawei, HiSilicon, Turkcell |
| R2-2402546 |
Discussion on early data transmission enhancements for IoT-NTN |
CMCC |
| R2-2402694 |
Discussion on EDT optimisation in IoT-NTN |
HONOR |
| R2-2402703 |
Discussion on uplink capacity enhancements for IOT NTN |
Xiaomi |
| R2-2402709 |
Discussion on enhanced EDT of IoT NTN |
CAICT |
| R2-2402716 |
EDT for uplink capacity enhancement in NTN |
Lenovo |
| R2-2402811 |
Discussion on EDT enhancements |
Qualcomm Incorporated |
| R2-2402887 |
Uplink capacity enhancement in IoT NTN |
Apple |
| R2-2402943 |
Discussion on enhanced EDT |
MediaTek Inc. |
| R2-2403042 |
On signalling overhead reduction for EDT in IoT NTN |
CATT |
| R2-2403126 |
Consideration on EDT enhancement for IoT-NTN |
NEC Corporation. |
| R2-2403206 |
Clarifications on the Scope of EDT enhancement for IoT-NTN |
Interdigital, Inc. |
| R2-2403338 |
Initial discussions on uplink capacity enhancements |
Samsung |
| R2-2403483 |
On uplink capacity enhancement for IoT NTN |
Nokia, Nokia Shanghai Bell |
| 8.10.1 |
Organizational |
|
| R2-2403564 |
Workplan for Rel-19 SON_MDT Enhancement |
China Unicom |
| 8.10.2 |
MRO enhancements for Rel-18 mobility features |
|
| R2-2402281 |
Discussion on LTM MRO enhancement |
Fujitsu |
| R2-2402551 |
Discussion on MRO enhancements for R18 mobility features |
CMCC |
| R2-2402564 |
MRO for Rel-18 mobility features |
vivo |
| R2-2402588 |
Discussion on random access report for LTM |
ASUSTeK |
| R2-2402632 |
MRO for Rel-18 mobility |
ZTE, Sanechips |
| R2-2402654 |
Discussion on MRO Enhancements for Mobility |
CATT |
| R2-2402735 |
Discussion on MRO for LTM |
Lenovo |
| R2-2402736 |
Discussion on MRO for CHO with candidate SCGs |
Lenovo |
| R2-2402965 |
Discussion on MRO enhancements for Rel-18 mobility features |
NEC |
| R2-2403137 |
MRO enhancement for SON and MDT |
Qualcomm Incorporated |
| R2-2403164 |
MRO enhancement for Rel-18 mobility |
Huawei, HiSilicon |
| R2-2403198 |
MRO for LTM |
Nokia |
| R2-2403199 |
MRO for CHO with candidate SCGs |
Nokia |
| R2-2403212 |
Discussion on MRO enhancement for Rel-18 mobility features |
Langbo |
| R2-2403243 |
SON support for MRO |
Ericsson |
| R2-2403270 |
SON/MDT reports for LTM |
Kyocera |
| R2-2403499 |
MRO enhancements for Rel-18 mobility features |
Samsung |
| R2-2403565 |
Discussion on MRO enhancement for mobility |
China Unicom |
| R2-2403579 |
MRO enhancement for LTM |
SHARP Corporation |
| 8.10.4 |
Leftovers from Rel-18 |
|
| R2-2402554 |
Discussion on SONMDT enhancements for SDT and MHI |
CMCC |
| R2-2402565 |
RACH optimization for SDT |
vivo |
| R2-2402633 |
Rel-18 leftovers for SON MDT |
ZTE, Sanechips |
| R2-2402655 |
Consideration on leftovers from Rel-18 SONMDT |
CATT |
| R2-2403138 |
SON and MDT Rel-18 leftover issues |
Qualcomm Incorporated |
| R2-2403165 |
Discussion on support of the Rel-18 leftovers |
Huawei, HiSilicon |
| R2-2403455 |
SON/MDT enhancements for leftover topics from R18 |
Samsung |
| R2-2403566 |
Discussion on RACH optimization for SDT |
China Unicom |
| R2-2403580 |
RA report enhancement for SDT |
SHARP Corporation |
| R2-2403664 |
On Rel.18 leftovers |
Ericsson |
| 9.1 |
Session on LTE V2X and NR SL |
|
| R2-2403731 |
Report from session on LTE V2X and NR SL |
Vice Chairman (Samsung) |
| 9.2 |
Session on NR MIMO evolution and Multi-SIM |
|
| R2-2403732 |
Report from session on R18 MIMOevo, R18 MUSIM, and R19 LP-WUS |
Vice Chairman (CATT) |
| 9.3 |
Session on NR NTN and IoT NTN |
|
| R2-2403733 |
Report from Break-Out Session on NR NTN and IoT NTN |
Session chair (ZTE) |
| 9.4 |
Session on positioning and sidelink relay |
|
| R2-2403734 |
Report from session on positioning and sidelink relay |
Session chair (MediaTek) |
| 9.5 |
Session on Mobility Enh and Mobile IAB |
|
| R2-2403735 |
Report from session on Mobility Enh, Mobile IAB and LP-WUS |
Session chair (MediaTek) |
| 9.6 |
Session on MBS and QoE |
|
| R2-2403736 |
Report from session on R18 MBS, R18 QoE and R19 XR |
Session chair (Huawei) |
| 9.9 |
Session on maintenance and eRedCap |
|
| R2-2403737 |
Report from maintenance, SON/MDT and eRedCap breakout session |
Session chair (Ericsson) |
| 9.10 |
Session on further NR coverage enhancements |
|
| R2-2403738 |
Report from Further NR coverage enhancements session |
Session chair (ZTE) |